Add Roslyn code analyzer for non existent component parameters or VS options

[ErikApption]

Visual Studio seems to be checking the parameters of blazor components and does highlight in red when a parameter cannot be bound.

However, this doesn't get caught by any Roslyn code analyzers and it will fail during execution with

blazor.server.js:1  [2024-03-15T19:55:34.506Z] Error: System.InvalidOperationException: Object of type 'Datahub.Portal.Layout.WorkspaceSidebar' does not have a property matching the name 'BadParameter'.
   at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.ThrowForUnknownIncomingParameterName(Type targetType, String parameterName)
   at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.SetProperties(ParameterView& parameters, Object target)
   at Microsoft.AspNetCore.Components.ComponentBase.SetParametersAsync(ParameterView parameters)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)

I suspect there might good reasons that this is not possible through Roslyn code analyzers, but any chances for a Visual Studio setting to bump these red things into errors?

[davidwengier]

Looks like this might be the same issue that #9144 is proposing to solve. Not sure if there is an issue to dupe it against though?

[jjonescz]

There's an issue in aspnetcore repo: #11114

[jaredpar]

Going to close this and let the aspnetcore issue be primary.