Disable pooling allocator automatically in environments where it will fail

[lann]

There are (at least) two environments where the Wasmtime pooling allocator is known to fail with Spin's default settings:

QEMU: #1785
Systems with <2GB (?) RAM: #2119

Under spin up we should try to detect either of these environments and disable pooling (with a message) to improve UX.

[lann]

Ideally this could be done by trying some operation known to fail with pooling (and retrying with pooling disabled to confirm) at boot time rather than detecting these specific issues, as long as this check is reasonably quick.

That might just be any module instantiation under the proper engine config.

[lann]

bytecodealliance/wasmtime#8610 would likely work for this