Put only hard fingerprinted files into import map during publish

[maraf]

The WriteImportMapToHtml feature is meant for Wasm/Blazor standalone scenarios. During development, those apps are serve through DevServer which integrates StaticWebAssets runtime features and provide a correct routing for soft fingerprinted files. In production, StaticWebAssets runtime features are not available, as those apps are typically hosted as static sites. That means we should put only hard fingerprinted assets into import map.

Pull Request Overview

This PR updates the asset fingerprinting behavior during publish so that only hard fingerprinted files are included in the import map for static sites.

• Added new properties (Assets, IncludeOnlyHardFingerprintedModules) and refactored the fingerprint replacement logic.
• Updated resource creation to check asset metadata for hard fingerprinting and modified related tests to validate both build and publish scenarios.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

File	Description
src/StaticWebAssetsSdk/Tasks/WriteImportMapToHtml.cs	Refactored fingerprinting logic and resource creation to conditionally include only hard fingerprinted assets.
test/Microsoft.NET.Sdk.Razor.Tests/StaticWebAssetsFingerprintingTest.cs	Updated tests with additional parameters and helper methods to cover the new fingerprinting behavior.

Comments suppressed due to low confidence (2)

src/StaticWebAssetsSdk/Tasks/WriteImportMapToHtml.cs:176

• The expression 'integrity ??= [];' uses invalid syntax for initializing a dictionary. Replace it with 'integrity ??= new Dictionary<string, string>();'.

integrity ??= [];

src/StaticWebAssetsSdk/Tasks/WriteImportMapToHtml.cs:184

• The expression 'imports ??= [];' is not valid for dictionary initialization. Use 'imports ??= new Dictionary<string, string>();' instead.

imports ??= [];