feat: allow to configure HPA and VPA for any service

[Ian2012]

Description

This PR allows configuring HPA and VPA for multiple services. It's a backward-compatible change as the old variables are used as defaults for the CMS, LMS, LMS-WORKER, and CMS-WORKER.

Author concern:

• After comparing the main branch vs. this PR, I only see one difference in the generated configuration. This is because the CMS was using the configuration for the CMS-WORKER.

 apiVersion: apps/v1
 kind: Deployment
@@ -44,11 +47,12 @@ spec:
         - name: cms
           resources:
             requests:
-              memory: 750Mi
-              cpu: 0.175
+              memory: 350Mi
+              cpu: 0.25
             limits:
-              memory: 3000Mi
+              memory: 1400Mi
               cpu: 1
+

Is this intended?

[jfavellar90]

@Ian2012 for now I'm closing this PR. The changes you propose will cause the creation of multiple configurations that can be complicated to maintain. There's an open discussion here where we are discussing the best way to provide HPA for additional OpenedX services.