docs: Clarified web worker type: 'module' is compiled away

[Pyrolistical]

Description

Documentation states type: 'module' is supported, but unclear it is correctly compiled away in production. This PR clarifies that.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

This addition makes it sounds like you can only use import when using type: 'module' and that isn't the case. Could you expand on what you find confusing here?
Maybe it could be:

Suggested change

	The worker script can also use `import` statements (with `type: 'module'` option) instead of `importScripts()` - note during dev this relies on browser native support and currently only works in Chrome, but for the production build it is compiled away.
	The worker script can also use `import` statements (both for classic and `type: 'module'` workers) instead of `importScripts()` - note during dev this relies on browser native support and currently only works in Chrome, but for the production build it is compiled away.

[Pyrolistical]

Hmm but now it sounds like you could use import statement in classic type

[patak-dev]

Yes, you can use it in classic types. It will be bundled and compiled away

[Pyrolistical]

Oh I didn't know that. What is the point of the module type then?

[sapphi-red]

It works when ?worker is used.
But it does not work in dev when new Worker(new URL('./foo.js', import.meta.url)) is used (#8470).

[patak-dev]

And @Pyrolistical, the module type controls how it is bundled in production (but should still be able to use ES modules to do your workers in both, except for the bug that @sapphi-red just linked)