[FEATURE]: Add component types to better support container orchestration environments

[Yaytay]

The list of valid component types is rather limited and this makes tools such as Dependency Track less useful when trying to work with container orchestration environments - essentially everything has to be either Application or Container.

I would like to propose:

• Cluster
  A collection of components that function together as a unit.

  For my purposes this would be either a Kubernetes or Swarm cluster, but it would serve equally in other situations.
  "Environment" would work as well as "Cluster", but I think "Cluster" is more generically useful.

• Service
  An abstract grouping of software components that provides some kind of end point for use by other components.

[jkowalleck]

FYI:

for these purposes, several properties are registered:

• rad:kbom:k8s:cluster https://github.com/rad-security/kbom/blob/main/docs/taxonomy.md
  rad:* was formerly ksok:*
• other proprietary ones

for these purposes, the community tried to consolidate - see CycloneDX/cyclonedx-property-taxonomy#59

[Yaytay]

@jkowalleck,
The problem with properties is that, whilst they do capture the data, there aren't many tools that know what to do with them.
In particular Dependency Track is not going to let me filter by properties, which is pretty fundamental when working with component types.

[jkowalleck]

The problem with properties is that, whilst they do capture the data, there aren't many tools that know what to do with them.

I see.
You should raise tickets to tool manufacturers, let them know which features you really need and why. (see for example: DependencyTrack/dependency-track#2614)