Investigate using custom Certificate Authority (CA) in end-to-end tests that use TLS

At present, the end-to-end tests that use TLS make use of self signed certificate that is not trusted by the browser by default. To instruct the browser to accept the certificate, we set acceptInsecureCerts to true. This is not a true reflection of the production environment.

This issue is to investigate using a custom Certificate Authority (CA) in end-to-end tests and document the way forward.

Here are some steps that we would need to be performing in addition to what we are already doing today:

1. Create a Certificate Authority (CA) which is basically a root certificate (hereinafter called root CA).
2. Use the root CA to create domain validation certificates for the domains used in the dest. (eg. https://gitlab.test)
3. Place the root CA in the system trusted store (/usr/local/share/ca-certificates/extra ??) on the container that will execute the test. We would probably need to do that in the qa-image's Dockerfile.