Web Components: Provide CDN version of pre-built bundle with dotcom-shell

The problem

Many of our v18 users want to use our library not requiring heavy toolstack but just with loading .js/.css.

Web Components library tried to meet such requirement with ECMAScript module, but it’s blocked by:

1. No browser has implemented import maps spec, that is required for browser to understand import { LitElement } from 'lit-element' code (to figure out where lit-element module .js file is)
2. Some CDNs (e.g. JSPM/UNPKG) tries to make above work by replacing NPM module name with actual CDN path on-the-fly, but it has performance problem by having to load many modules, and tends to hit many glitches

The solution

Create pre-built bundle.

Additional information

• We can make use of the EI server and upload to there (https://1.s81c.com/common/ibm-dotcom-library/@{version}/**)

Acceptance criteria

• Create generated bundle that includes the dotcom-shell
• Publish up to EI server (beta, next and latest)

[jeffchew]

@asudoh as discussed, if you can open a PR with the build mechanism (rollup), I will hook up the CI part of it.

[jeffchew]

To catch up on this, a couple of issues were raised to the webmaster team:

• Create the folder /common/ibm-dotcom-library for us on the production server
• Open cross origin calls to the akamai server (it is currently only open for www.ibm.com

With this, the pipeline has been built out, but to a temporary folder that our team has access to on the production environment. This story can only be completed up to the release of automated beta releases, as we do not currently have a release candidate or full release with the build script available in the codebase. An additional story will be created to capture the closure of that.