Add resource limits to Ansible operator scaffolding

[asmacdo]

The Helm operator scaffolds resource limits in the manager manifest:

operator-sdk/internal/plugins/helm/v1/scaffolds/internal/templates/config/manager/manager.go

Lines 78 to 84 in 24d73f7

	resources:
	limits:
	cpu: 100m
	memory: 90Mi
	requests:
	cpu: 100m
	memory: 60Mi

However these resource limits were too restrictive for ansible operators. Since v0.19 scaffolded Ansible operators do not have resource limits, I am considering this a new feature that can be added post 1.0 release.

[camilamacedo86]

It is important because common attacks take advantage of it. See; https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html#rule-7-limit-resources-memory-cpu-file-descriptors-processes-restarts

PS. The default values are not enough for Ansible. So, the complexity here is to find what values should be appropriated.

[asmacdo]

Some research is needed to determine what these default values should be. We have deprioritized for now-- please feel free to chime in or open a PR with suggested defaults.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale