feat: support experimental.async and dynamicCompileOptions for Svelte modules

[dominikg]

resolves #1174

Due to the way CompileOptions extends ModuleCompileOptions and how compileModule throws an error if you pass in an unknown option, simply forwarding the complete compileOptions would cause validation errors.

This PR prevents that by filtering with known module option names, which is going to require future updates for any new option that has to be passed.

An alternative could be to filter remove known non-module options. This makes it easier to introduce new module options, but new non-module options would then require updating the list to avoid them causing a validation error on compileModule.

[dummdidumm]

Good interim solution 👍
Filtering for known module compile options is better I think, since it's less likely that we add new module options vs new Svelte component options