feat: API V2 - Local dev only for now

[jgadling]

This PR adds a v2 GraphQL API based on the work in the platformics repo. For now it includes its own (slightly modified) version of the base platformics codebase, while we wait for several changes to the base library to be merged upstream. We'll eventually pull in the platformics library from pypi to avoid maintaining multiple copies.

The schema is in apiv2/schema/schema.yaml and the GraphQL API that gets generated is relatively similar to the interface presented by Hasura, except that all 1:many relationships implement the Relay connection spec. That means if we have an API V1 query that looks like this:

query MyQuery {
  datasets {
    id
    runs {
      id
    }
  }
}

It will look like this in API V2:

query MyQuery {
  datasets {
    id
    runs {
      edges {
        node {
          id
        }
      }
    }
  }
}

Currently this new API isn't integrated into the same local dev environment as the rest of the containers when running make init from the root of the repo. I'm hoping to address that in a later PR.

[manasaV3]

nit: is File being used?

[jgadling]

Nope. I'm not sure why ruff isn't removing these unused imports but they're harmless.

[manasaV3]

It is interesting that we are using a different account for storing the images. Is there any specific reason on why we aren't storing it in the relevant account?

[jgadling]

It's just the way the argus team has things set up by default :'( eventually I'd like it to pull from github's image repo, but it doesn't seem worth fighting with right now.

[manasaV3]

nit: should we rename this? 😁

[jgadling]

ehhh, we're eventually going to be using the upstream platformics package and this stuff can go away, but in the meantime it's 🤷‍♀️ ... we can clean it up when we delete the platformics directory here?

[manasaV3]

I feel this shouldn't be an enum at the db level, because in the case we want to have a combination of tomogram and annotation, we would have to create a new type.

[jgadling]

We have a 1:many relationship between depositions and this deposition_types_enum via the DepositionTypes type!