Add io.rsocket metadata

[oracle]

Add io.rsocket metadata

[sureshg]

@sdeleuze jfyi: this is fixed in the latest GraalVM CE dev (java 19) release. My app is working fine now.

[sdeleuze]

We potentially need to copy and adap Netty native config to cover the shaded one provided with RSocket.

[sdeleuze]

Those hints are now provided directly by RSocket JAR so you can close this issue as not planned / won't fix.

[sureshg]

@sdeleuze would it work for rsocket-kotlin also? When I tried a few days back, I was getting some wiered error for rsocket-kotlin (coming from ktor client dependency)

Fatal error: com.oracle.graal.pointsto.util.AnalysisError$ParsingError: Error encountered while parsing io.ktor.client.engine.cio.CIOEngine.<init>(io.ktor.client.engine.cio.CIOEngineConfig)
Parsing context:
   at io.ktor.client.engine.cio.CIOEngine.<init>(CIOEngine.kt)
   at io.ktor.client.engine.cio.CIO.create(CIOCommon.kt:35)
   at io.ktor.client.HttpClientKt.HttpClient(HttpClient.kt:41)
   ....
   Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Discovered a type for which getDeclaringClass0 cannot be called: io.ktor.util.CoroutinesUtilsKt$SilentSupervisor$$inlined$CoroutineExceptionHandler$1. This error is reported at image build time because class io.ktor.util.CoroutinesUtilsKt$SilentSupervisor$$inlined$CoroutineExceptionHandler$1 is registered for linking at image build time by command line
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.SVMHost.handleLinkageError(SVMHost.java:426)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.SVMHost.getDeclaringClass(SVMHost.java:412)
	......
Caused by: java.lang.IncompatibleClassChangeError: io.ktor.util.CoroutinesUtilsKt and io.ktor.util.CoroutinesUtilsKt$SilentSupervisor$$inlined$CoroutineExceptionHandler$1 disagree on InnerClasses attribute
	at java.base/java.lang.Class.getDeclaringClass0(Native Method)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor$NativeAccessor.invoke0(Native Method)

[sdeleuze]

As far as I know, recent versions of rsocket-kotlin are based on a different Kotlin multiplatform implementation, so no those matadata should not cover it. Also the error looks like Ktor specific.