Support configuring the root component name

[ertl]

Is your feature request related to a problem? Please describe.

The plugin currently derives the root component from the package.json in the repository root.

This causes an incorrect root component when using a monorepo, where the root package.json represents the repository/workspace rather than the individual application being bundled.

The webpack plugin already provides configuration options for this use case, including:

rootComponentAutodetect
rootComponentName
rootComponentVersion

For example, the webpack plugin allows configuring the root component name explicitly when autodetection is disabled.

Describe the solution you'd like

Add the same functionality to this plugin.

Contribution

• I am willing to provide an implementation
• I will wait until somebody else implements it

[jkowalleck]

CycloneDX is a community effort.
feel free to contribute the missing feature.

[wizlor-bfw]

Opened a PR: #203

Ported `rootComponentAutodetect`/`rootComponentName`/`rootComponentVersion` from `cyclonedx-webpack-plugin`'s implementation. One difference worth flagging: this plugin's `BomBuilder` builds the main component up front and folds it into the same component map used for dependency linking, so overriding it needed an extra step the webpack plugin's flow doesn't: explicitly dropping the auto-detected component from `bom.components` once it's replaced, otherwise it lingers as a duplicate regular component alongside the override. Caught that empirically while inspecting the generated bom.json, not just from reading the code.

Added an integration testbed (`with-root-component-override`) plus a direct check of the dependency-re-pointing logic against the compiled output.