issue(install): missing resources config on controller-manager

Description

Decided to give this operator another try since it matured to v1.0 with the hope that we could migrate our current Helm based runner deployment over to this, however I got stuck instantly during install. A short investigation later, the gitlab-runner-controller-manager failed to get scheduled due to it not setting resource requests/limits and us enforcing them to be required via Resource Quotas. I know I could have added a Limit Range to circumvent this, however, our operation team encourages us not to use them and set the resources for our deployments accordingly, so I refrained from doing so and halted my testing for now.

Thank you for your work on this!

Expected behaviour

The Operator can be installed no matter if the OCP project has setup resource quotas or not.

Workaround

Configure a Limit Range on Containers so the not resource tagged gitlab-runner-controller-manager Replica Set can get scheduled.

Screenshots