Container Registry configuration workflow

What does this MR do?

Container Registry configuration workflow

Add types and workflow to render the Container Registry configuration.

The container registry is handled in two workflows/templates:

1. A workflow/template for the configuration handling
2. A worklow/template to manage workload and networking resources

Splitting the workflow allows:

1. Easier management of the checksum to re-rollout the Container Registry on changes.
2. Separation of concerns: The workload and networking resources do not need access to referenced secrets (e.g. the AWS secret) at templating time.

Author's Checklist

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Ensure a release milestone is set.
• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• MR has a green pipeline on GitLab.com.
• When ready for review, MR is labeled workflowready for review per the MR workflow.

Expected

• Test plan indicating conditions for success has been posted and passes.
• Documentation is created or updated.
• Tests are added.

Test Plan

1. Deploy the Operator with Container Registry enabled
2. Confirm the configuration Secret is applied.

Related issues

Relates #8