Implement support for strict Content-Security-Policy (MapLibre usage)

### Describe the problem

Hello, currently when using this library with a Content-Security-Policy policy, users are forced to use ```worker-src blob:``` which is inherently unsafe due to it being functionally equivalent to ```unsafe-eval```. This is due to the usage of maplibre-gl. This would be generally seen as a pretty notable hole in a deployed Content-Security-Policy.

### Describe the proposed solution

maplibre-gl has a CSP variant of it's JS bundle, per: https://maplibre.org/maplibre-gl-js/docs/#csp-directives It would be greatly appreciated if support for this was implemented, as then a much more fine grained and significantly less vulnerable Content-Security-Policy can be leveraged.

### Alternatives considered

_No response_

### Additional Information

_No response_

Start by tracing how this library integrates and bundles maplibre-gl, then compare that path with MapLibre's documented CSP variant and directives. Done means users can enable the CSP-compatible bundle without requiring worker-src blob:; verify the integration with the repository's existing checks.

Written by the indexing model from the issue text.