Annotate WebAssembly.Authentication

[pranavkm]

Fixes #30751
Fixes #35162

[TanayParikh]

LGTM, just some formatting nits

[pranavkm]

Authentication.MSAL was already annotated for trimming. However WebAssembly.Authentication previously wasn't. Investigating this issue, the underlying issue was that our JSRuntime.Invoke* APIs aren't annotated accurately. Essentially, all of the args array is subject to serialization constraints, but we don't express this. Unfortunately, the best we could do is slap a RequiresUnreferencedCode on these methods.

In this particular case, MsalProviderOptions is passed as a JSRuntime.InvokeAsync argument but was being trimmed (all of the getters were being removed). Annotating the entry point as this PR does helps, but it would help to revist JSRuntime's annotations.

[TanayParikh]

Annotating the entry point as this PR does helps, but it would help to revist JSRuntime's annotations.

Do we have a tracking issue for this?

[SteveSandersonMS]

Great that you were able to resolve the issue with the authentication libraries!

Investigating this issue, the underlying issue was that our JSRuntime.Invoke* APIs aren't annotated accurately. Essentially, all of the args array is subject to serialization constraints, but we don't express this. Unfortunately, the best we could do is slap a RequiresUnreferencedCode on these methods.

By that do you mean we're unable to annotate them because the right kinds of annotation don't exist and we'd need to ask for new compiler features, or do you mean we can and should put [RequiresUnreferencedCode] on the interface methods?