[kong] able to configure resources for all containers

[zjheyvc]

What this PR does / why we need it:

Adds configurable block of resources for migrations containers when are needed to use, useful when use namespaces with quotas.

Also, Inherit resources from Kong pods for others containers to this approach

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

• fixes Implement requests/limits for all containers #264

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• PR is based off the current tip of the next branch and targets next, not main
• New or modified sections of values.yaml are documented in the README.md
• Title of the PR and commit headers start with chart name (e.g. [kong])

[CLAassistant]

All committers have signed the CLA.

[rainest]

@julianvelizc and @zjheyvc can you sign the CLA? Code changes look good, so once that's signed we can merge it in.

[zjheyvc]

@julianvelizc and @zjheyvc can you sign the CLA? Code changes look good, so once that's signed we can merge it in.

Hello @rainest , I did signed with @zjheyvc but I think with my another account is not possible to connect to github to signed it license, what can I do continue in this case?

[zjheyvc]

If is not possible, we can close this PR and I will send another just with my active user @rainest

[rainest]

You'll want to re-author the commits to your zjheyvc user following https://www.git-tower.com/learn/git/faq/change-author-name-email/

After that force-pushing the branch should fix this PR.

[zjheyvc]

@rainest its done!