chore: Drop adminClient (1/2)

[DafyddLlyr]

What does this PR do?

• Belated follow on to feat: Create new api role in Hasura #2294
• Remove adminClient (still in "god mode" using the Hasura admin secret)
• Replace with permission scoped $public or $api clients
• I've split this in two to keep things simpler and smaller. Part 2 here!

Principles

• Queries should be typed (by default planx-core is returning an unknown otherwise). For simplicity I've just used the mutation / query name as the interface name. If this isn't clear / meaningful I can append a Query / Mutation suffix.

• Where possible, use queries as the place where we convert snake_case (from the db) to camelCase (in the application). This means our interfaces and types are all camelCase as expected. This has meant cascading (noisy) changes to code and tests but it seemed worthwhile over introducing more snake_case properties to types.

• Allow $api client for side-effects triggered by permission-scoped users (such as writing audit logs). The alternative here would be to increase public client scope and add backend-only mutations - see previous thoughts on this here.

[github-actions]

Removed vultr server and associated DNS entries

[github-actions]

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

Updated Tables (1)

• public.reconciliation_requests permissions:

  	insert	select	update	delete
  api		➕

  5 added column permissions

  	insert	select	update
  api		➕ created_at ➕ id ➕ message ➕ response ➕ session_id

[DafyddLlyr]

This was required to give the API role access to the insert_reconciliation_requests_one mutation.

insert_<object>_one will only be available if you have select permissions on the table, as it returns the inserted row

Docs: https://hasura.io/docs/latest/mutations/postgres/insert/#insert-a-single-object

[DafyddLlyr]

What's going on here?

CoreDomainClient client is being mocked so that we can control and modify the behaviour of formatRawProjectTypes() and test it.

However, we want to retain the behaviour of CoreDomainClient.client so that real GraphQL queries get made so that graphql-query-test-mock is able to catch and mock these calls. To do this we can use jest.requireActual to maintain this behaviour.

I feel like there's possibly a few more elegant options here - I'd like to revisit this.

[DafyddLlyr]

This structure is repeated a few times throughout this PR. I spent a good bit of time attempting to generalise it so that we could import it with an interface similar to -

function mockCoreDomainClient(customMocks = {}) {
   const actualCoreDomainClient = jest.requireActual(
    "@opensystemslab/planx-core",
  ).CoreDomainClient;

  return {
    CoreDomainClient: class extends actualCoreDomainClient {
      constructor() {
        super();
        Object.assign(this, customMocks)
      }
    }
  }
}

...

mockCoreDomainClient({
  formatRawProjectTypes: () => mockFormatRawProjectTypes(),
});

Tried a few variations without much success - I suspect the problem is related to how Jest is hoisting mocks (through the jest.mock("@opensystemslab/planx-core") notation). I wanted to just move on as opposed to losing more time here so I'll open a GitHub issue describing this.

[DafyddLlyr]

Issue logged here - #2404

[jessicamcinchak]

Thanks for following through with all these updates and thorough explanations of how you've set up mocks here!

Left a few naming suggestions for clarity, but overall looks good 👍