Add support to overwrite the init containers CPU requests

[ShinyDhas]

We updated the community operator from 0.7.0 to 0.13.0
Although initially everything was installed without any issues, we noticed all the Mongodb CR were in Pending state in kubernetes cluster.
After troubleshooting we found that init containers such as readiness probe and mongod-post hook requests for 500m of CPU time which is very high. We want to be able to change the requests through the operator itself. But we noticed that the operator injects these values internally, which is very difficult to manage as platform team.

Please add support to be able to modify the init containers on the CR.

[github-actions]

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.