[wasi] Add build support for using wasm-opt

[radical]

This adds the build support but does not enable it by default which can be enabled with $(WasmRunWasmOpt)=true.
Also, a new wasm-props.json file is added to the wasi runtime pack. For browser this is emcc-props.json with a new name.

• [wasm/wasi] Add new wasm-props.json to the runtime pack
  For browser this is emcc-props.json renamed. And for wasi, it's a new
  file.
• [wasm/wasi] Extract target for running wasm-opt, and use for both browser, and wasi

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This adds the build support but does not enable it by default which can be enabled with $(WasmRunWasmOpt)=true.

• [wasi] Add WasiSdkPath to WasmToolchainEnvVars
• [wasm] Move wasm-opt to common targets
• cleanup
• [wasm] set some properties before importing common targets

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Build-mono
Milestone:	-

[radical]

Update: TODO: wasm-opt run should respect incremental builds

[radical]

TODO:

• check for any regression in file sizes with browser, and blazor

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[maraf]

Looks good to me 👍

[maraf]

Should we remove the target?

[radical]

I want to implement this in a future PR.

[radical]

The hybrid globalization failures are not specific to this PR, and filed as #95983 and #95981 .