[release/8.0-staging][wasm] remove problematic default settings

[lewing]

Part of dotnet/aspnetcore#52947

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[lewing]

This probably still doesn't fully resolve the linked issue but there are others that are related.

[vitek-karas]

The majority root cause of the linked issues is that trimmer removes parameter names from methods (.ctors) - this is problematic for serialization of KeyValuePair for example as the logic there relies on the parameter names.
This change modifies trimming of attributes and nullability info (attributes which encode the ? in C#) - I don't see how that will fix the original problem. As seen in the comments the workaround was to tell trimmer to not remove parameter names. If we can't fix the reflection any other way, I would suggest we add that to the default settings for trimmer for Blazor instead.

@sbomer for trimmer official guidance, I don't work on it directly anymore.

[sbomer]

That issue also mentioned #81979 which was fixed in .NET 9. Does the issue repro when targeting net9.0? If this fixes it we could consider backporting #102850 to .NET 8.

[akoeplinger]

That issue also mentioned #81979 which was fixed in .NET 9. Does the issue repro when targeting net9.0? If this fixes it we could consider backporting #102850 to .NET 8.

We removed setting the switches (same change as this PR) in #102934 for 9.0 so it's hard to say.