Deploy Kubernetes operators as docker containers for Mock server.

[gabrielpetry]

Summary

This PR enhances our capabilities for mocking and deploying in Kubernetes. It introduces new operators and providers to simulate a more realistic environment, enabling the deployment of complex resources via CRDs.

What's New

In addition to the noop-provider (used to provision fake PVCs), we are now deploying:

• Prometheus Operator: Handles the management of Prometheus deployments.
• MongoDB Community Operator: Enables MongoDB management via Custom Resource Definitions (CRDs).

Context & Impact

Previously, certain resources could not be simulated in full. With these additions, the manually deployed container can now successfully interact with the mock server to create resources defined by operators.

Example Use Case:
We can now deploy a MongoDB instance using the standard CRDs from the Mongo operator within our mock environment:

apiVersion: [mongodbcommunity.mongodb.com/v1](https://mongodbcommunity.mongodb.com/v1)
kind: MongoDBCommunity

In the image: mongodb-kubernetes-operator-679c97777-kxl4z is the fake operator, which is incapable of doing anything because it is fake, but given that we have the operator container running from the docker-compose, it was able to deploy the fake sts of MongoDB.

For future reference, each operator requires a distinct configuratino, overall, the easier way is to set the environment variables KUBERNETES_MASTER and KUBECONFIG, but some operators, like mongo, require extra environment variables to work. The easier way is to describe the pod generation and just copy the environment into the Docker Compose.

[gabrielpetry]

Closed in favor of https://github.com/RocketChat/helm-charts/pull/225/changes#diff-1edefa9210988edbffca7cc4ae769750a1541b90a0045513311812b4bf0bc22f