fix(rendering): Allow memory sizes between 2gb and 4gb by using wasm allocation

[wayfarer3130]

Context

Browsers don't allow allocation of more than 2gb memory using the standard buffer allocators. This PR adds the ability to allocate using the WebAssembly.Memory allocator, which seems to work fine up to 4 gb, although the GPU does complain about memory texture size limits.

Changes & Results

Added a test example, using local data for now (and so not in the shared examples), plus changed the createFloat32SharedArray to use WebAssembly.Memory

Testing

Deploy the test data to localhost:5000/dicomweb
Run
yarn example volumeLarge
View the page, should display (may still be browser dependent).

Checklist

PR

• [] My Pull Request title is descriptive, accurate and follows the
  semantic-release format and guidelines.

Code

• [] My code has been well-documented (function documentation, inline comments,
  etc.)

• [] I have run the yarn build:update-api to update the API documentation, and have
  committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

• [] The documentation page has been updated as necessary for any public API
  additions or removals.

Tested Environment

• [] "OS:
• [] "Node version:
• [] "Browser:

[netlify]

✅ Deploy Preview for cornerstone-3d-docs ready!

Name	Link
🔨 Latest commit	a18ec5a
🔍 Latest deploy log	https://app.netlify.com/sites/cornerstone-3d-docs/deploys/664cb229d9431b0008138082
😎 Deploy Preview	https://deploy-preview-1260--cornerstone-3d-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[IbrahimCSAE]

works great on orthanc but seems there's some issues when using P10 dicom from local

[sedghi]

worked great, see my FYIs that i fixed