[Blazor] Remove blazor script check

[javiercn]

Summary of the changes

• Removes the check that we have to produce an error when you include a script tag inside a Razor file.
• We used to have this check to preclude people accidentally adding script tags to their components, since in the context of interactive rendering it does not do what they expect.
• As we are rendering components statically in .NET 8.0, this warning/errors creates more problems than it solves, and there is no reason for us to keep it around, and instead, we will let the customers do as they see fit.

Fixes:
#8743

[itsmuntadhar]

also helps if you have to have a specific script for a specific page/component and don't want to load it everywhere, i.e. putting it in index.html.

[javiercn]

/AzurePipelines run razor-tooling-ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[javiercn]

@chsienki can you take a look?

[chsienki]

LGTM. @333fred or @jjonescz for a second review.

[davidwengier]

For my interest/knowledge, should this be gated by a razor version or TFM check or something? I worry that someone will open a project in VS that targets an old SDK, not get warnings about their script tags, but then when they do a command line/CI build they will.

[333fred]

I'm not too worried about the warning difference, but I'll ping @jaredpar for his thoughts/awareness as well.

[javiercn]

Thanks for the review folks!