[wasm] Allow to build browser in library mode

[mkhamoyan]

By this PR we are supporting library mode for browser.

Contributes to #77191

[mkhamoyan]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[lewing]

Needs follow up on existing comments

[mkhamoyan]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[lewing]

This feels wrong, we're plumbing the rid down to the generator rather than dealing with runtime init ordering in the browser case. I'd rather we unconditionally emit the intiialize_runtime call and have it assert when it can't actually do the initialization.

[maraf]

This feels wrong, we're plumbing the rid down to the generator rather than dealing with runtime init ordering in the browser case. I'd rather we unconditionally emit the intiialize_runtime call and have it assert when it can't actually do the initialization.

We are initializing runtime for browser in the place™️ manually. I guess we can have wrap the mono_wasm_load_runtime in initialize_runtime for browser case, still call it manually and leave the generator untouched