fix: use names from resources directly

[Andor]

Description

Currently, if you override for any reason Prometheus' ServiceAccount name, the related subject name will not change.

The workaround is to override subject alongside with overriding ServiceAccount name, which is not ideal.

          serviceAccount+: {
            metadata+: {
              name: 'my-serviceaccount-name',
            },
          },
...
          clusterRoleBinding+: {
            subjects: [{
              kind: 'ServiceAccount',
              name: 'my-serviceaccount-name',
              namespace: 'my-namespace',
            }],

The same for Role and ClusterRole name in RoleBinding and ClusterRoleBinding accordingly.

This patch fixes this behaviour and you will be able to override

Type of change

What type of changes does your code introduce to the kube-prometheus? Put an x in the box that apply.

• CHANGE (fix or feature that would cause existing functionality to not work as expected)
• FEATURE (non-breaking change which adds functionality)
• BUGFIX (non-breaking change which fixes an issue)
• ENHANCEMENT (non-breaking change which improves existing functionality)
• NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry

Please put a one-line changelog entry below. Later this will be copied to the changelog file.

Use ServiceAccount, Role and ClusterRole names in RoleBinding and ClusterRoleBinding referencing from the according resources instead of generating on the spot.

[Andor]

Apparently tests are failing for non-related reason.

[philipgough]

Apparently tests are failing for non-related reason.

Correct, CI was broken but is back green now. Triggered this again.

[Andor]

@philipgough much appreciate mate.
Now it is all green.