[browser] Lazy loading should be extension agnostic

[maraf]

• Both parts of lazy loading definition requires to use assembly file name (including extension)
• With webcill an extension for assembly changes from .dll to .wasm
• Current behavior requires to change lazy loading definition when switching between webcil and non-webcil
• Ideally lazy loading definition should be without file extension
• Making both extensions work is a blocker, because JS part of the runtime doesn't currently know if webcil was used or not. We probably could check for file with user passed extension in assets and if not found, check for .wasm

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

Issue Details

---

• Both parts of lazy loading definition requires to use assembly file name (including extension)
• With webcill an extension for assembly changes from .dll to .wasm
• Current behavior requires to change lazy loading definition when switching between webcil and non-webcil
• Ideally lazy loading definition should be without file extension
• Making both extensions work is block, because JS part of the runtime doesn't currently know if webcil was used or not. We probably could check for file with user passed extension in assets and if not found, check for .wasm

Author:	maraf
Assignees:	maraf
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript, os-browser
Milestone:	9.0.0