Create unique DT-projects per k8s cluster

[salvabot0001]

Changelog

Add support for kubernetesClusterIdMode configuration in DependencyTrack integration

This solves #822

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 11.54%. Comparing base (09054d3) to head (edd2343).
⚠️ Report is 282 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/target/dtrack/dtrack_target.go	0.00%	7 Missing ⚠️
internal/processor/processor.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #823       +/-   ##
===========================================
- Coverage   25.13%   11.54%   -13.59%     
===========================================
  Files           6       13        +7     
  Lines         565     1386      +821     
===========================================
+ Hits          142      160       +18     
- Misses        406     1203      +797     
- Partials       17       23        +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ckotzbauer]

Hi @salvabot0001,
thanks for opening this PR. As the new KubernetesCommonPrefix is very similar to the existing KubernetesClusterId I would prefer to not introduce a new flag with a similar purpose. I would suggest to introduce another flag DtrackKubernetesClusterIdMode instead or similar named which has two possible values: tag (default) and prefix. tag would preserve the current handling inside the dtrack_target.go were the cluster-id is used as project-tag. The new prefix mode could be used instead of tagging for the prefixing you introduced.
WDYT?

[salvabot0001]

Hi @ckotzbauer,

thanks for the fast reply. I agree with you here. I will adjust the PR with your suggestion.