Enable CORS for legacy bundle loading

[steverep]

Proposed change

Enables CORS mode for both the entry scripts and tags added by Webpack.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[bramkragten]

What is the reasoning behind this? Will this not give issues with custom ES5 modules like it did when we tried this for modules? #6745

[steverep]

What is the reasoning behind this?

1. My thought was so there are no restrictions on error logging, but disregard that as I see now it only applies when it's actually not the same origin
2. So that if or when webpackPreload is used for the modern build, it works (i.e. <link rel="modulepreload" ... />)

Will this not give issues with custom ES5 modules like it did when we tried this for modules? #6745

Yeah, you're right it probably would. I'll remove that.

[steverep]

Okay I removed it for custom scripts. So now it's on/off equivalent to the modern build.