feat: resource workload configuration support

[shreddedbacon]

This is a WIP for being able to template basic resource workload implementations (HPA/PDB) and eventually resources per service overrides (requests/limits).

Currently the requests/limits overrides are ignored in the templating stage as these are currently done in an odd way that requires a bit more work to override (mainly that service templates are still done in helm, so can't benefit from the way the build-deploy-tool generates values)

The way to consume this currently is to set a LAGOON_FEATURE_FLAG_WORKLOAD_RESOURCES envvar, which is a base64 encoded JSON value.

The structure of which looks something like this, which is a map[string]structure where the string = the parameter name which is to be consumed, and the structure is the data payload contained within which can define the hpa, pdb, and eventually resources, that should be applied to any services that match the servicetype and request the workload resources by name

{
    "nginx-php-performance": {
        "serviceType": "nginx-php-persistent",
        "hpa": {
            "spec": {
                "minReplicas": 8,
                "maxReplicas": 16,
                "metrics": [
                    {
                        "type": "Resource",
                        "resource": {
                            "name": "cpu",
                            "target": {
                                "type": "Utilization",
                                "averageUtilization": 3000
                            }
                        }
                    }
                ]
            }
        },
        "pdb": {
            "spec": {
                "minAvailable": 2
            }
        }
    }
}

Currently, a user needs to specify the workloadresource to consume using a label in docker-compose.yml like so, and the build will fail if the requested workloadresource is not for the requested service-type that the workloadresource is defined for

    labels:
      lagoon.type: nginx-php-persistent
      lagoon.workloadresource: nginx-php-performance

It is also possible to specify workloadresource assignment via an envvar override type similarly to how dbaas and service type overrides work(but as a feature flag for now), where it is serviceName:workloadResource. This allows for updates to workload resources without requiring the docker-compose file to be modified. API wins out over docker-compose defined workload resources too.

LAGOON_FEATURE_FLAG_WORKLOAD_RESOURCE_TYPES=nginx:nginx-php-performance