Cranelift: roll forward to RA2 once bytecodealliance/regalloc2#218 is fixed

[cfallin]

Because this results in an infinite loop (due to disagreement about the definition of a minimal bundle between the predicate and the splitting code), and because the code is present in 0.11.3, we have yanked 0.11.3. The released Wasmtime will continue to use 0.11.2, and main will be able to use 0.11.3 due to its lockfile, but we will need to fix the issue and roll forward to a new RA2 (or else roll back the try-call and retval-inst PRs #10510 and #10502) before our next release is cut.

[cfallin]

This has a fix in bytecodealliance/regalloc2#220, awaiting review. I'll release a new (not semver compatible!) RA2 once that lands.