chore(scripts): remove cdn from webpack configs

[jmfrancois]

What is the problem this PR is trying to solve?

We have now a code base which is aligned with mainstream patterns but still a way to compute external from the code which is too complex.

What is the chosen solution to this problem?

Let's remove it from the webpack config and see the impact.
Teams can already test by using the following configuration in talend-scripts.json

 { "dynamic-cdn-webpack-plugin": false }

Please check if the PR fulfills these requirements

• The PR have used yarn changeset to a request a release from the CI if wanted.
• The PR commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features) And non reg done before need review
• Docs have been added / updated (for bug fixes / features)
• Related design / discussions / pages (not in jira), if any, are all linked or available in the PR

[ ] This PR introduces a breaking change