fix(one-app-dev-cdn): handle uncaught promise

[JAdshead]

Description

update to one-app-dev-cdn which includes handling of promise created when fetching remote module map during development

Motivation and Context

Better error message when fetching invalid module map

How Has This Been Tested?

locally using valid and invalid module maps.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

[github-actions]

📊 Bundle Size Report

file name	size on disk	gzip
app.js	276KB	81.5KB
runtime.js	15.6KB	5.5KB
vendors.js	124.8KB	38.3KB
app~vendors.js	430KB	112.4KB
service-worker-client.js	17.1KB	5.3KB
legacy/app.js	296.4KB	86KB
legacy/runtime.js	15.6KB	5.5KB
legacy/vendors.js	183.1KB	49.5KB
legacy/app~vendors.js	453.6KB	118.4KB
legacy/service-worker-client.js	17.6KB	5.5KB

Generated by 🚫 dangerJS against a9bea46