[BREAKING] Discontinue bundling of JavaScript modules as string

[flovogt]

The UI5 bundler packages JavaScript files that are identified as "requiresTopLevelScope" as a string, to be evaluated via "eval" at runtime. This behavior ensures that the script works as expected, e.g. with regards to implicit globals.
This "eval" runtime feature with be discontinued in UI5 2.0 because of security best practices (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) and to comply with stricter CSP settings (unsafe-eval).
By using specVersion 4.0 an error is thrown when bundling a module as string and the module is not included in the bundle at all.

JIRA: CPOUI5FOUNDATION-794

[coveralls]

coverage: 94.681% (+0.01%) from 94.668%
when pulling f617f0b on disable-string-bundling
into 51e2b08 on main.

[coveralls]

coverage: 94.681% (+0.01%) from 94.668%
when pulling f617f0b on disable-string-bundling
into 51e2b08 on main.

[coveralls]

coverage: 94.681% (+0.01%) from 94.668%
when pulling 136b40d on disable-string-bundling
into 51e2b08 on main.

[coveralls]

coverage: 94.681% (+0.01%) from 94.668%
when pulling 2b4a4dc on disable-string-bundling
into 51e2b08 on main.

[coveralls]

coverage: 94.645% (-0.02%) from 94.668%
when pulling 8791491 on disable-string-bundling
into 934956a on main.

[coveralls]

coverage: 94.668%. remained the same
when pulling 88bcad2 on disable-string-bundling
into 934956a on main.

[coveralls]

coverage: 94.677%. remained the same
when pulling f8e4b88 on disable-string-bundling
into dfa67fe on main.

[RandomByte]

I'm missing some tests for the case of specVersion 4 project with resources that require bundling as string

[coveralls]

coverage: 94.677%. remained the same
when pulling 2781bfe on disable-string-bundling
into dfa67fe on main.

[flovogt]

ui5 tooling integration tests are triggered: 534

[RandomByte]

LGTM

[KlattG]

@flovogt I think I've seen 'higher' more often than 'newer'.

[KlattG]

LGTM

[KlattG]

Just one minor point, otherwise LGTM