Add reources management for nodes

[puppetninja]

This is a duplicated one of #502, PR generated from official repo branch to run all the CI jobs

This PR would set the resource manage for octez nodes and sidecar in the same pod. For bakers, there are no resources management for it however

Users can manage the node resources for octez node placement. Additionally, users can use k8s autoscalers to scale out node pods based on certain criteria
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale
This scaling mechanism is for pod, so both octez node and sidecar resources should be specified for the pod resource usage to be calculated. For now, pods with bakers running inside is not supported.

[nicolasochem]

This still requires "documentation" in the chart's default values.yaml

What we typically do is provide a commented-out example in the values file, with some additional explanatory commentary.

[nicolasochem]

it looks like you can simply pass "resources" $.node.vals.resources and if the key is absent it would pass null, and still work? So you can avoid setting $bakerParams at all and just modify the dict passed to include "tezos.generic_container".

[nicolasochem]

Why assign requests to the baker as well as the node? Then if you set requests of 3300Mi on a baking node, the pod actually requires 6600Mi. and more if you have more bakers. Can we set a request for the node only, so the value configured ends up being the total pod request?

[nicolasochem]

@harryttd @orcutt989 all issues resolved, please review again

[orcutt989]

@nicolasochem @harryttd There are still requested changes on this PR. Please dismiss them if they have been addressed.

[harryttd]

I'm reviewing right now

[harryttd]

Almost ready. I think i understand the PR more fully now. I didn't get that the scaler wouldn't scale if it was targeting specific containers as opposed to the entire pod resources. So if it couldn't find any resources defined on any container it wouldn't scale.