feat: Metabase dashboard service and controller (re-pushed)

[zz-hh-aa]

Re-pushed version of #4150 hopefully sidestepping the Vultr phishing issue (Slack thread here).

What does this PR do?
Creates services getDashboard, copyDashboard, updateFilter and generatePublicLink
Adds necessary types and tests
Creates new route for analytics module
Exports the Metabase client as a singleton instance (this also happens in 8f12f20 in #4072 but there were other changes in the same commit so I've isolated the change here)
Updates Swagger yaml
Why?
Following on from #4072, this should complete all the services we need to automate Metabase dashboard creation
This PR became a bit bigger than I'd anticipated... let me know if it'd be better to break it up!

[github-actions]

Removed vultr server and associated DNS entries

[jamdelion]

Shaping up nicely! A few pointers for refactoring and type strengthening 💪

[jamdelion]

Nice one! Extremely minor nits but happy for you to change them and merge whenever suits :)

[DafyddLlyr]

Shaping up great! A few comments around types, error handling and snake_case.

Tests look great and descriptive, this is really very close just a few small things to iron out.

Very happy to catch up and talk through feedback if any of it is unclear - please just let me know.

[DafyddLlyr]

We should find a good way of handling this issue of Metabase using snake_case but our API using camelCase.

All requests and responses to Metabase must be in snake_case, but any internal types passed around our API (as well as requests and response to our API) should be in camelCase.

There's a number of ways of handling this, one could be a Metabase types module so that we can type them as Metabase.GetDashboardResponse (namespaces are sort of deprecated / not recommended in TS).

We can assign these types to our client (axios already supports these generics) -

const response = await $metabase.get<Metabase.GetDashboardResponse>(`/api/dashboard/${dashboardId}`);

Then, if we're returning from out internal functions, we should use camelCase types (map across).

I appreciate this is a bit tedious/repetative but it's worth doing and avoid a lot of confusion down the time. Happy to talk this one through if you'd like 👍

[zz-hh-aa]

I think I'm a little confused on this one and could do with talking it through!

I'm wondering if a.) since this PR is convoluted enough as it is (especially since I just rebased and added a bunch of other commits 😬) and b.) since this matter involves the collection/ folder as well, if it would make sense to talk about this next week and figure out a solution that will work across the Metabase module?

[DafyddLlyr]

Yep - on board with this, happy to park for now and we can catch up this week about it. Please send across a calendar invite for a time that works for you 👍