Fix Azure Maps Grid worker bundling and refresh dependencies

[rhanoudi]

What changed

• Refreshes AzureMapsGrid's compatible runtime and PCF build dependencies, including Azure Maps Control 3.7.4, react-azure-maps 1.0.3, React/ReactDOM 17.0.2, and pcf-scripts 1.51.1.
• Enables custom webpack configuration and aliases azure-maps-control to its prebuilt UMD bundle.
• Excludes that prebuilt Azure Maps bundle from Babel retranspilation.
• Imports the required Azure Maps stylesheet.
• Bumps the control version to 0.0.257 and solution version to 1.0.199.

No PCF properties, authentication behavior, dataset logic, or public TypeScript interfaces change.

Why

ft error when the map first loads.

After the dependency refresh, AzureMapsGrid could show several related browser errors:

• A 400 response for the legacy road sprite URL.
• Cannot read properties of undefined (reading 'bing-mvt').

The stylesheet import is also required by Azure Maps for correct map layout and assets.

Validation

• Clean install with Node.js 22.23.2: npm ci.
• Direct dependency verification: npm ls --depth=0.
• Production PCF build: npm run build -- --buildMode production.
• Release solution build using MSBuild, producing both managed and unmanaged packages with zero packaging errors.
• Verified both archives contain solution 1.0.199 and control 0.0.257.
• Verified the archived bundles match the tested production bundle exactly.
• Verified the broken worker helper pattern occurs zero times, native worker destructuring remains present, and Azure Maps CSS is embedded.
• Smoke-tested the managed solution in Dataverse/Chrome; the map loads and the reported console errors are resolved.

Webpack reports only its existing bundle-size performance advisory for the approximately 2 MiB control bundle.