control-service: add the frontend to helm

[murphp15]

What

Within the introduction of the frontend docker image we want it to appear when ppl visit the host url.

How

In this PR we introduce:

1. a new deployment and service to support running the frontend.
2. an ingress rule to send requests from the root of the host to the frontend and an ingress rule to send any requests for /data-jobs to the control-service.
3. Support for reading the frontend docker image from a private repo which is something we need within VMWare.
4. Update the control-service to the a newer version
5. add support for basic configuration of the frontend service e.g. how much cpu the deployment is given.

What is not in this PR:

1. passing configuration to the frontend via properties or volumeMounts.

How has this been tested

Locally

[ivakoleva]

Before this PR, if ingress was enabled the control-service was mapped to the root of the host url.
After this PR,

frontend-ui is mapped to the root of the host url.
control-service is mapped to /data-jobs

May you also elaborate on Swagger UI?

[murphp15]

Before this PR, if ingress was enabled the control-service was mapped to the root of the host url.
After this PR,
frontend-ui is mapped to the root of the host url.
control-service is mapped to /data-jobs

May you also elaborate on Swagger UI?

@ivakoleva there is no impact on the swagger url as that starts with /data-jobs.
In fact no endpoint urls for the control-plane are changed so I am going to remove the breaking-change section from the description.