[Blazor] Detect pre compressed assets in packages, avoid compressing those assets and emit a warning instead

[javiercn]

Some existing packages ship already compressed versions of assets without the appropriate metadata that conflict with the paths we generate for our own compressed assets.

Instead of erroring out, avoid compressing that asset and emit a warning to indicate the situation.

[mkArtakMSFT]

Cleaning the milestone to re-triage.

[davhdavh]

This is pretty critical, noone in our team can upgrade to vs 17.12 since it kills all old builds

[gadjio]

Is it possible that it also affect AzureDevops build pipeline

https://github.com/actions/runner-images/blob/win22/20241113.3/images/windows/Windows2022-Readme.md

---

After troubleshooting, I was able to resolve the problem by specifying a stable SDK version in my global.json file. I set it to use .NET SDK 8.0.100, which bypassed the error completely.

For anyone else facing this issue, here’s the global.json configuration that worked for me:
json

{
  "sdk": {
    "version": "8.0.100"
  }
}

This solution forces Azure DevOps to use the specified version (8.0.100) instead of the default (9.0.100), which seems to have compatibility issues in this scenario. Hopefully, this helps others until a fix is available in .NET SDK 9.x.