Fix for Dockerfile conflict with sonar + agent and tools missing distros propagation

[MaciejKaras]

Summary

Fixes issue with conflicting Dockerfile files on master. Sonar is creating Dockerfiles in the directory where new Dockerfile existed already. They were added here -> #289.

Additionally another PR #267 made changes to how the agent images were built and especially to agent Dockerfile ARGs:

mongodb-kubernetes/docker/mongodb-agent/Dockerfile

Lines 3 to 6 in 89866b7

	ARG agent_version
	ARG agent_distro
	ARG tools_version
	ARG tools_distro

This conflicted with #303 where new atomic_pipeline.py was still depending on the old Dockerfile structure:

mongodb-kubernetes/docker/mongodb-agent/Dockerfile

Lines 25 to 26 in 774bbac

	ARG mongodb_tools_url_ubi
	ARG mongodb_agent_url_ubi

Proof of Work

Passing CI (especially agent build task)

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.3.0 Release Notes

Bug Fixes

• This change fixes the current complex and difficult-to-maintain architecture for stateful set containers, which relies on an "agent matrix" to map operator and agent versions which led to a sheer amount of images.
• We solve this by shifting to a 3-container setup. This new design eliminates the need for the operator-version/agent-version matrix by adding one additional container containing all required binaries. This architecture maps to what we already do with the mongodb-database container.

Other Changes

• Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
• subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.