[PM-13650] Use transpiled JS build

[dani-garcia]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-13650

📔 Objective

We're bundling the transpiled WASM to JS SDK, but never actually using it. This PR loads the transpiled JS when WASM isn't supported.

I've also added typing support for the init function.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
  team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
  issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 4f53f68f-b6e4-4df2-be60-d673841538fd

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Unpinned Actions Full Length Commit SHA	/build-swift.yml: 95	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-swift.yml: 136	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-swift.yml: 73	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-rust-crates.yml: 76	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 44	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-internal.yml: 61	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-internal.yml: 67	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.86%. Comparing base (3800954) to head (576fdb7).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   62.86%   62.86%           
=======================================
  Files         179      179           
  Lines       12685    12685           
=======================================
  Hits         7974     7974           
  Misses       4711     4711           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Hinton]

I abandoned this approach since it turned out we need to do this differently depending on what client we build for. This logic now lives in the clients repository.

https://github.com/bitwarden/clients/blob/main/apps/web/src/app/platform/web-sdk-client-factory.ts

[dani-garcia]

Hmm, when I tested it last week it was using the DefaultSdkService without fallback for web and browser, weird. I've tested it again now and the fallback is working correctly, so seems like I accidentally misconfigured something.