gh-100340: Allows -Wno-int-conversion for wasm

[kushaldas]

Adds new configuration directive to disable int-conversion and then using it for the wasm32-wasi build only. This allows us to build on the version 17 of the wasm-sdk.

How to test manually?

Install the version 17 of the SDK and then run the following command:

./Tools/wasm/wasm_build.py wasi

• Issue: Build failure on wasm-sdk-17 #100340

[brettcannon]

I looked at the output for https://buildbot.python.org/all/#/builders/1046 , but I couldn't find any way to tell what version of the WASI SDK was used to build Python. I know that @tiran set up the buildbots using https://github.com/tiran/ansible-wasm-buildbot .

[kushaldas]

I looked at the output for https://buildbot.python.org/all/#/builders/1046 , but I couldn't find any way to tell what version of the WASI SDK was used to build Python. I know that @tiran set up the buildbots using https://github.com/tiran/ansible-wasm-buildbot .

@brettcannon The buildbot is using version 16 according to https://github.com/tiran/ansible-wasm-buildbot/blob/main/roles/wasi-sdk/defaults/main.yml#L3

[erlend-aasland]

LGTM!

[kushaldas]

This worked on wasi-sdk-19 too.

[brettcannon]

@kushaldas any reason this wasn't backported?

[merwok]

Came here from your recent blog post — as a small build change that can be considered a bug fix, and would give the benefit of keeping various python versions compatible with the latest wasi runtime, this seems fine to backport!

[miss-islington]

Thanks @kushaldas for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

[bedevere-bot]

GH-106066 is a backport of this pull request to the 3.11 branch.