Fix/System-config secret hash trigger

[slopezz]

• Adds the secret hash rollot trigger to system-config secret, which is defined on a CR field because it is managed externally to saas-operator, unlike the rest of the secrets that are managed as ExternalSecrets inside saas-operator
  • So right now, if there is a change on that external secret mounted on System saas-operator deployments/statefulsets (all except sphinx), a rollout will be automatically triggered so new created pods will load new secret values
• Creates alpha release v0.18.0-alpha.10 that has been tested successfully in staging:

      annotations:
        saas.3scale.net/system-recaptcha.secret-hash: 6fd87786b8
        saas.3scale.net/system-backend.secret-hash: 7d69d9698b
        saas.3scale.net/system-master-apicast.secret-hash: 68c799f75b
        saas.3scale.net/system-events-hook.secret-hash: 6b99695c69
        saas.3scale.net/stg-saas-system-config.secret-hash: 7f9955868b  ## THIS
        saas.3scale.net/system-zync.secret-hash: 85c5cc6498
        saas.3scale.net/system-smtp.secret-hash: 54d765bf5c
        saas.3scale.net/system-multitenant-assets-s3.secret-hash: 7959c58cdd
        saas.3scale.net/system-app.secret-hash: 7b87786f7d
        saas.3scale.net/system-database.secret-hash: 7886f9678f

/kind bug
/priority important-soon
/assign

[3scale-robot]

LGTM label has been added.

Git tree hash: 6ea58701bec89de58360efbfe05d0eec17999e5c

[slopezz]

/approve

[3scale-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: slopezz

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 [slopezz]

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