Fix issue with traefik issueing certificates with letsencrypt acme

[costrouc]

The core of the issue was that for entrypoints a default certResolver
was not being specified. Additionally had to read some docs within
traefik https://doc.traefik.io/traefik/routing/entrypoints/#tls that
state that is a tls = {} section is specified within the crd
ingressroute the tls configuration is overwritten.

If a TLS section (i.e. any of its fields) is user-defined, then the
default configuration does not apply at all.

Fixes #1015

Changes:

• changes related to traefik ingress

Types of changes

What types of changes does your code introduce?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

Tested locally using minikube and using digitalocean

Requires testing

• Yes
• No

In case you checked yes, did you write tests?

• Yes
• No

[costrouc]

Still need to test with custom secret for compatibility. So do not merge until this is tested.

[costrouc]

Tested and this appears to be working great with all three methods of creating certificates. This also appears to fix the dask-gateway issue when visiting the link. With the exception that self signed certificates are not trusted. This is due to issue thomseddon/traefik-forward-auth#122. So the dashboards for now will only work for trusted certificates.