KUBESAW-16: Label the token secrets

[metlos]

Make sure the secret containing the creds for clients connecting between clusters is labeled as belonging to its ToolchainCluster resource.

This will be used in the future to base the creation of the ToolchainClusters on the existence of such secrets.

Associated PRs:

• toolchain-cicd: KUBESAW-16: Label the secrets with the access tokens for toolchain clusters toolchain-cicd#109
• api: Add the definition of the toolchain-cluster label to the API so that it can be reused freely throughout the codebase. api#423
• host-operator: KUBESAW-16: Update the go.mod to use toolchaincluster controller from the toolchain-common KUBESAW-16 host-operator#1030
• toolchain-e2e: KUBESAW-16: Label token secrets toolchain-e2e#970

[codecov]

Codecov Report

Attention: Patch coverage is 57.89474% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 77.87%. Comparing base (0cabe6c) to head (3027359).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #396      +/-   ##
==========================================
- Coverage   78.06%   77.87%   -0.20%     
==========================================
  Files          47       47              
  Lines        1965     1984      +19     
==========================================
+ Hits         1534     1545      +11     
- Misses        373      378       +5     
- Partials       58       61       +3     

Files	Coverage Δ
...rs/toolchaincluster/toolchaincluster_controller.go	61.53% <57.89%> (-2.10%)	⬇️

[MatousJobanek]

Looks good, but let's also cover the error case when the update would fail.
Are you going to create also a e2e test for it?

[mfrancisc]

Nice Job 👍

one minor question - should we add a test case for "secret not found" ?

[metlos]

one minor question - should we add a test case for "secret not found" ?

good point 👍🏼 it's added.

[mfrancisc]

thanks for addressing my comments!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
6.7% Duplication on New Code

See analysis details on SonarCloud