[llvm] Ensure NoTrapAfterNoreturn is false for the wasm backend (PR #65876)

[Matt Harding via llvm-commits]

majaha wrote:

Hmm. It's not that the two options are incompatible with Wasm per se. Rather, overriding their values is an implementation detail of the Wasm backend. The implementation could change in the future, making the options meaningful for the Wasm backend again, and we don't want to be adding or removing errors and warnings over implementation details changing.

I don't think other target options work the way you suggest, do they? Is there any precedent for that?

https://github.com/llvm/llvm-project/pull/65876