[JS/WegGPU] Initial changes to support wasm64.

[satyajandhyala]

Description

Changes to support wasm64.

Motivation and Context

[satyajandhyala]

@dakenf, I have some changes from your PR to enable wasm64. I am running into the following error
Error: no available backend found. ERR: [webgpu] RuntimeError: Aborted(Assertion failed: JSPI not supported by current environment. Perhaps it needs to be enabled via flags?)

Using either of the following commands:
npm test -- model test\data\node\opset8\test_add -x 1 -b=webgpu --chromium-flags=--experimental-wasm-memory64 --chroumim-flags=--enable-experimental-webassembly-jspi
or
npx karma start --browsers ChromeCanaryTest --single-run --force-localhost --bundle-mode=dev --chromium-flags=--enable-features=SharedArrayBuffer --chromium-flags=--experimental-wasm-memory64 --chromium-flags=--headless=new --chromium-flags=--enable-dawn-features=allow_unsafe_apis,use_dxc

[satyajandhyala]

@dakenf Is there any compiler option requires. I have commented-out protc target options in onnxruntime-webassembly.cmake

[satyajandhyala]

@fs-eire I enabled JSPI in ChromeCanary browser and npx uses ChromeCanary instead of Chrome. Still I am getting the error saying that the environment does not support JSPI. Any idea?

[satyajandhyala]

I have to pass enable-wasm-memorry64 option as follows to overcome the above mentioned error using --js-flags settings
npm test -- model test\data\node\opset8\test_add -x 1 -b=webgpu -e canary --chromium-flags=--experimental-wasm-memory64 --chroumim-flags=--enable-experimental-wasm-memory64 --chromium-flags=--js-flags=--experimental-wasm-memory64

[satyajandhyala]

/azp run Big Models Linux Android Emulator QNN CI Pipeline Linux CPU CI Pipeline Linux CPU Minimal Build E2E CI Pipeline Linux GPU CI Pipeline Linux OpenVINO CI Pipeline Linux QNN CI Pipeline MacOS CI Pipeline

[azure-pipelines]

No pipelines are associated with this pull request.

[satyajandhyala]

Opened a new PR with changed branch name.
#21836