Set JS runtime config from CLI for static modules

[jeffcharles]

Description of the change

Sets the JS runtime config for static Javy modules from the Javy CLI. Specifically it uses a WASI environment variable to pass the config bitflags when Wizer runs the initialization function. It uses the same Config:all() call as was in the main file for Core to initialize the configuration in the CLI.

Why am I making this change?

See #702. Specifically for the -J flags, I need a way to set the JS runtime configuration from the CLI.

I opted to use an environment variable because I need some way to pass the configuration into the initializer function. I'm open to other suggestions. Presumably we could use the same approach when emitting the provider for the emit provider command.

I'm opting not to bump the provider version in this PR because we're not changing the provider.

Checklist

• I've updated the relevant CHANGELOG files if necessary. Changes to javy-cli and javy-core do not require updating CHANGELOG files.
• I've updated the relevant crate versions if necessary. Versioning policy for library crates
• I've updated documentation including crate documentation if necessary.