Fix CSI credentials naming mechanism

[psalajova]

As of now, the new CSI mutli-stage step credential system creates one SecretProviderClass (SPC) per credential, mounted to the test pod in as a CSI volumeMount. Since we need to shard the existing credential secrets, like this:

credentials:
  - collection: team1
    name: name
    mount_path: /var/run
  - collection: team1
    name: diff-name
    mount_path: /var/run

the existing system resulted in Kubernetes's Invalid value: "<mount_path>": must be unique errors (see e.g. this test run), because even if this results in a volumeMount with different name, the mount_paths cannot be the same.
Also, because the credential's name can be quite long, we were hitting character limit exceeded errors.

Solution:

• Credentials with the same (collection, mountPath) are now grouped into a single SPC
• SPC names are based on a hash of collection, mount path, and credential names to prevent overwrites when different steps use the same collection/mount combination
• Truncation logic -- to stay within Kubernetes' 63-character DNS label limit -- was used for SPC and CSI volumes naming
• For sidecar censoring, all credentials are created as individual SPCs, with different names and mount paths

[danilo-gemoli]

I've noticed that this check happens in several places. If we forbid two credentials with the same name, wouldn't it be appropriate to add this policy to the code that validates a ci-operator configuration? pkg/validation/config.go

[psalajova]

This check is for the scenario when there's more steps in a workflow which use the same credentials. E.g. this workflow -- has steps stackrox-stackrox-begin and stackrox-stackrox-end, and both have the stackrox-automation-flavors credential in their definitions.

[psalajova]

/test e2e

[danilo-gemoli]

/lgtm

[openshift-ci-robot]

/test remaining-required

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danilo-gemoli, psalajova

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [danilo-gemoli,psalajova]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@psalajova: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/breaking-changes	2bc827a	link	false	/test breaking-changes

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2a5b667 and 2 for PR HEAD 2bc827a in total