Add config setter for wasm_component_model

[effulgentsia]

This adds the Go binding for recently merged bytecodealliance/wasmtime#12630.

While in there, I noticed that wasm_component_model was also missing a Go setter, so added it.

There's other C API config options without Go bindings, but they involve memory internals, exceptions, threads, or similar constructs that I'm unsure whether they require deeper Go code changes to support so I left those out of this PR.

Note that tests might fail if they run against v41 of wasmtime instead of HEAD since the gc_support setter was added to the C API after the v41 release.

[effulgentsia]

What's the preferred way to address these test failures? Some options I can think of, but there's probably others I'm not thinking of:

• Postpone this PR until after the gc_support setter is in a tagged wasmtime release.
• Update this repo's CI to test with wasmtime HEAD.
• Comment out the gc_support test addition until after a tagged wasmtime release but retain the setter addition itself.

[alexcrichton]

Wasmtime 42.0.0, which doesn't include the gc_support patch, is slated to be released tomorrow so Wasmtime 43, to be released March 20, will be the first to include gc_support. I'd prefer to keep this repo testing against the latest release if possible, so mind splitting this up to the component-model knob and the gc-support knob? I'll land the gc-support knob before releasing 43.0.0 here

[effulgentsia]

Ok, that makes sense. I updated this PR to only do wasm_component_model and I'll open a new PR for gc_support after this one is merged.