Draft: config: Disable container registry by default in gitlab config test env

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.

What does this merge request do and why?

config: Disable container registry by default in gitlab config test env

Certain tests expect that GitLab's container registry is disabled, e.g. spec/requests/admin/applications_controller_spec.rb . This means that these tests fail when GitLab's container registry is enabled in the config file for the test environment, i.e. gitlab.yml.

When the container registry is enabled in gdk.yml then it will also enable the container registry for test env.

This commit disables the GitLab container registry by default (ONLY) for the test environment. This way, the tests will pass even though the container registry is enabled in the gdk.yml.

🛠️ with ❤️ at Siemens

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.