Ensure ability to customize the HtmlEncoder used for the RazorComponentEndpoint

[SteveSandersonMS]

For reasons like this (thanks @DamianEdwards)

The default encoder settings are pretty aggressive/conservative, encoding anything above standard ASCII despite the response encoding generally being UTF8, so it's not unusual for folks to customize the encoder to be more lenient, for example allowing Katakana/Hiragana characters through without HTML encoding

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[DamianEdwards]

Turns out we already have mechanisms for this in ASP.NET Core via IServiceCollection.AddWebEncoders() so fixing this should just be a case of ensuring AddRazorComponents() calls that and that the component renderer resolves HtmlEncoder from DI.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[DamianEdwards]

@SteveSandersonMS @mkArtakMSFT @danroth27 why was this moved to the backlog? We have a long-established pattern of enabling customization of the HTML encoding in ASP.NET Core via the registered HtmlEncoder instance and Razor Components needs to honor that.