Add vpa crs for keda-operator and metrics-server

[QuantumEnigmaa]

This PR adds VPA CRs for both keda-operator and metrics-server.

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• README is updated with new configuration values (if applicable) learn more
• A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)

Fixes #

[QuantumEnigmaa]

I just noticed I forgot to sign my 2 previous commits :/

[tomkerkhove]

Can you remove the new artifacts please?

[QuantumEnigmaa]

@tomkerkhove I reverted the changes on the artefacts

[tomkerkhove]

This is automatically generated though: https://github.com/kedacore/charts/blob/main/CONTRIBUTING.md#documentation

[QuantumEnigmaa]

Do you mean I can get rid of this change in the PR as it will be automatically be run by the ci jobs ?

[JorTurFer]

I think that this is fascinating, but I'm not sure if it works correctly before the live pod resizing is in GA. I mean, restarting the operator for updating the pod size could produce scaling downtimes and we should clarify it IMHO. This also could generate impact on k8s api server on huge clusters if the VPA scales the pod so often because all the scalers cache has to be rebuilt on each restart, recovering all the needed info from the cluster