Change log for uiBundler

All notable changes to the package uiBundler are documented here.

Version 8.7.0

BundlerOptionsUserOverrideConfig, BundlerOptions
- Added USER level configuration to override options for bundler.

In 8.9.0, we will remove support for incremental bundling files in cssLibrary/src/stylesheets/*.scss. Please move your files to cssLibrary/resource/stylesheets/*.scss to ensure incremental bundling will work properly.

Webpack
- {app}/ui/c3/config/package-lock.json has been deleted and is no longer being used to lock js-webpack_c3 dependencies. Resolved runtimes are now being used and are already provided unless you add extra dependencies to js-webpack_c3.
- If a package is extending the js-webpack_c3 ImplLanguage.Runtime and used a hard-coded package-lock.json file in {app}/ui/c3/config/package.lock.json, the runtime needs to be resolved in that package to restore the locking functionality.
- If you extend js-webpack_c3 it is recommended that you resolve it in your package as you might encounter issues and will be enforced in a future version.

UiBundler
- developmentBatchSize will now default to 3. This means that if the UiBundlerConfig#developmentBatchSize is not defined in the root package, it will automatically default to 3 webpack configs bundled for each batch job. The previous default was to bundle all webpack configs in one single batch job.

UiContentHandler
- c3AppUrlPrefix cookie is always set for default content HTML, even when response is 304 NOT MODIFIED to ensure the document is always setting the right prefix for other assets.

UiBundlerConfig
- New configuration developmentBatchSize to control how many webpack configurations are bundled in a single batch when using development mode

UiBundler
- Update npm from version 6.14.14 to 7.24.2
- Install bundler from bundler/bundler.tgz REST endpoint