feat: update resource assignment

[cdobbyn]

Which problem is this PR solving?

There are two problems this solves:

1. There shouldn't be default resource assignments, the helm standard is to not assign but to recommend defaults as comments in the values file. The way it's configured today makes it so that by default this component uses WAY too many resources by default.
2. Individual containers should have their resources configured separately. Again the way this works today means this component uses too much resources.

Fixes: #853, #499

Short description of the changes

• default resource assignment to not have resource assignment
• make it so individual containers have separate resource assignment

Type of change

• New feature / enhancement (non-breaking change which adds functionality)

New Tests?

n/a

Checklist:

• Add changelog entry following the contributing guide
• Tests have been added
• Documentation has been updated

[CLAassistant]

All committers have signed the CLA.

[juanjjaramillo]

Closing this PR after having an internal discussion on the issues that can be generated if we do not set resource limits to our integration

[cdobbyn]

@juanjjaramillo I will open a separate PR for granular resource config (as I this is still necessary). Can I at least set the default requests lower than this? They are quite high for most clusters:

[cdobbyn]

@juanjjaramillo #918