feat: analytics module gets and updates PlanX DB

[zz-hh-aa]

What's new in this PR

• Migration to add metabase_id column to teams in PlanX DB
• Update Hasura permissions for api to be able to read and update relevant values
• A getTeamIdAndMetabaseId function
• An updateMetabaseId function
• Tests for the above

Why

• Daf suggested that a better pattern than querying Metabase every time we want to check if a collection exists would be to store a metabase_id in the PlanX DB and check that instead
• This is the PlanX DB portion of big PR wip: feat: collection service & controller #3971

[github-actions]

🤖 Hasura Change Summary compared a subset of table metadata including permissions:

Updated Tables (1)

• public.teams permissions:

  	insert	select	update	delete
  api		➕/➖	➕

  2 added column permissions

  	insert	select	update
  api		➕ metabase_id	➕ metabase_id

[github-actions]

Removed vultr server and associated DNS entries

[jamdelion]

Just hopping on as I realised I'd forgotten to review these for you! This is looking pretty good to me, though we are getting an integration test failure:

 FAIL  teams.test.js > teams > api > cannot create, update, or delete teams
Error: 'teams' unexpectedly found in mutation(s) [update_teams,update_teams_by_pk,update_teams_many]
 ❯ teams.test.js:102:17
    100| 
    101|     test("cannot create, update, or delete teams", () => {
    102|       expect(i).toHaveNoMutationsFor("teams");
       |                 ^
    103|     });
    104|   });

This is because we have added a mutation (update metabase ID in the teams table), where previously the api role did not have any mutations.

I guess we should update the test to instead expect the mutation (similar to the can query teams test in the same file)

[DafyddLlyr]

_ilike could match both "North Somerset" and "South Somerset" - it would be better to match using _eq on team slugs if possible which are guaranteed to be unique.

[zz-hh-aa]

Great catch! Updated in ba015dc.