Create alternative container rightsizing action execution to directly update pod resource

The idea is mimc vertical pod autoscaler (VPA https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler) initial mode.

"Initial": VPA only assigns resource requests on pod creation and never changes them later.

This is just another way to apply the recommended actions for resize (vertical only) when pods are created. What is nice about this approach would be that we don't need to update the source of truth since the original Deployment/Statefulset/Daemonset/etc will be untouched, only the pod runtime settings will be changed with a mutating webhook. The challenge would be to persist/cache recommended sizes on the remote clusters so that the webhook is as quick as possible.

PM Update:

The feature under consideration is to provide alternative mechanisms to apply Container Spec rightsizing actions in a k8s cluster. Today the OOTB mechanism involves updating the parent controller, which is a good strategy to persist and propagate the change across all replicas. However k8s does provide alternatives that could be useful options for those that want to operationalize Turbo without changing the parent definition.

Under consideration that will be handled in separate Master Epics:

1. Supporting in-place pod updates that would also not require a restart, which is beneficial to workloads that have a definition of state. Turbonomic will support when this project is beta. Current status is alpha as of 1.27: https://kubernetes.io/blog/2023/05/12/in-place-pod-resize-alpha/

2. Provide a Turbo mutating webhook to be used in versions of k8s until in-place pod update is beta. Here Turbonomic should improve of what VPA does and apply the change to all running replicas, given that our analysis is designed to provide a better definition of consistent scaling across all replicas.