[release/8.0] [browser] Add EmccMaximumHeapSize to define maximum memory

[github-actions]

Backport of #91256 to release/8.0

/cc @maraf

Customer Impact

Add user an easy way to declare a maximum memory that the app has access to.

Testing

Manual

Risk

None. No change by default

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[ghost]

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

Issue Details

---

Backport of #91256 to release/8.0

/cc @maraf

Customer Impact

Add user an easy way to declare a maximum memory that the app has access to.

Testing

Manual

Risk

None. No change by default

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	arch-wasm, area-Build-mono, os-browser
Milestone:	-

[lambdageek]

@maraf @lewing We should add something to https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/blazor about making Blazor apps for mobile devices. In particular it seems like apps that want to support mobile Safari will need <EmccMaximumHeapSize>268435456</EmccMaximumHeapSize> (256MiB). Not sure if we have any specific Android guidance.