Provide a way to override operand image, env, and resources in CRD

[MikeEdgar]

This change deprecates the existing images and env properties of the CRD and replaces them with per-container objects to specify a container image, env, and resources (cpu/memory).

Currently in the Console CR, API container ENVs and override images can be given like

spec:
  env:
  - name: SOME_ENVVAR
    value: "custom-value"
  images:
    api: example.com/myorg/my-api-image:1.0
    ui: example.com/myorg/my-ui-image:1.0

The new way with the change is:

spec:
  containers:
    api:
      image: example.com/myorg/my-api-image:1.0
      resources:
        limits:
          cpu: 500m
          memory: 256Mi
      env:
      - name: SOME_ENVVAR
        value: "custom-value"
    ui:
      image: example.com/myorg/my-ui-image:1.0
      resources:
        limits:
          cpu: 500m
          memory: 256Mi
      env:
      - name: SOME_ENVVAR_UI
        value: "custom-value"

Both sets of properties are still mapped to the console deployment, but the old properties are marked as deprecated in the CRD descriptions.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[MikeEdgar]

@k-wall, I'm curious to get your thoughts/feedback on the proposed CRD format in the description.