chore: improvements to local development for easier use of lagoon

[shreddedbacon]

General Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

Database Migrations

• If your PR contains a database migation, it MUST be the latest in date order alphabetically

Just restructuring the make file to make local experience better. The main changes are in the charts repo which is where a lot of the main make logic lives.

Key things:

• installs metallb and cert-manager into k3d
  • metallb allows for creating loadbalancers in k3d that get their own dedicated IP address within the docker network of k3d. this means users don't have to add :32080 or :32443 to ingress etc
  • cert-manager will provision self-signed certificates when the kubernetes.io/tls-acme annotation is present
• make k3d/setup will now spin up a k3d and install lagoon to an operational point. this lets someone spin up lagoon to a point where they can basically "just use it".
• new make k3d/local-stack will create a k3d cluster, install lagoon, load some seed data and seed users and present credentials to log in and start using it straight away in a fully functional local stack
• new make k3d/get-lagoon-details will return more useful information that allows someone that has run make k3d/setup to access this lagoon quicker (it would be nice if we could seed some user accounts like this)
• mac users: https://github.com/chipmk/docker-mac-net-connect mac users can use this to allow access to the services created using metallb
• all the docker-compose deployed versions will also get the seed users added now too

[tobybellwood]

This is great - I'll make the changes to the charts to accommodate it