FIPS Support

#### Feature

I'd like to be able to run a build of Wasmtime that has `wasi-http` configured to run in FIPS mode. This would mean that all https requests and responses would use a NIST-certified crypto module.
This could just be a separate build of Wasmtime and wouldn't need to be dynamic per-request or per-VM.

#### Benefit

If I want to run Wasmtime in a US Gov "FedRAMP Moderate" or higher environment, I need to be able to show auditors that any encryption-in-transit is done with a crypto module that's been NIST-certified as FIPS-140-2 or FIPS-140-3 compliant. As an example, the Golang 1.24+ crypto module 1.0.0 was just [validated last week](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/5247), so any golang programs [built with the appropriate flags](https://go.dev/doc/security/fips140#the-gofips140-environment-variable) are guaranteed to use the appropriate crypto implementation. Ideally Wasmtime could support something similar for its WASI implementations.

#### Implementation

It looks like wasi-http depends on rustls:
https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi-http/Cargo.toml#L43

I'm not a rust expert, but I believe Rustls can support support FIPS via the aws-lc-rs backend
* https://github.com/rustls/rustls/issues/1540#issuecomment-1943348533
* https://docs.rs/rustls/latest/rustls/crypto/fn.default_fips_provider.html

This could potentially allow either a FIPS build of Wasmtime, or for FIPS a mode to be surfaced via config.

Here's are the NIST certificates for the various versions of the aws-lc crypto module:
https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search?SearchMode=Basic&ModuleName=aws-lc&CertificateStatus=Active&ValidationYear=0

#### Alternatives

1. Have wasi-http delegate to [wasi-crypto](https://github.com/wasm-crypto/wasmtime-crypto) and have wasi-crypto be the one that supports FIPS at a lower-level. This would be a more generic solution, making FIPS also available to applications that are using wasi-crypto instead of just consumers of wasi-http, but that also increases the API surface area and scope of this request. My use case only require https requests and responses go through a NIST-certified crypto module, so a narrower scoped solution seemed the best incremental approach. If successful, wasi-crypto could still be considered in a future iteration, but might use aws-lc-rs directly instead of going through rustls.
2. Allow some other way to plugin in a FIPS-140-3 compliant crypto module. If this doesn't ship as part of Wasmtime, it would make the setup of the containerd shim in SpinKube more complicated.
3. Implement a pure-wasm implementation of the crypto and get it NIST certified. This would be an extremely lengthy and expensive process, which doesn't seem worth the effort when there are multiple performant solutions available within the ecosystem that have already been validated and certified. I admit it would be cool though.