Remove bundle.js from the repo: it's a generated artefact.

[joanise]

bundle.js is generated by our deployment workflows, so the version in the git repo is never used. We should simply remove it and fully embrace that it's generated.

Related to #284 and #184

I expect this is what's needed:

• git rm the bundle
• add it to .gitignore
• make sure deployment and testing, both in CI and locally, still work (they should)

[sergeleger]

I think we could also remove assets/fonts.b64.css for the same reason.

We'll need a method to generate those files in local environments. Preferably in an automated fashion. Manually running npx nx bundle web-component is an option but it will need to be documented.

Should the following lines (from bundle.sh) be protected by a flag, so that it only happens in production builds? This would limit the git diff noise bundle.sh will generate.

cd ../studio-web
npm pkg set singleFileBundleVersion="${packageVersion}"
npm pkg set singleFileBundleTimestamp="${timestamp}"

[joanise]

I need to think about this one more carefully. Might be worth meeting to discuss it. Food for thought: do those fields even still belong in the package.json if the files are generated?