Deprecate the old (v1) API

[jgadling]

Related epic: #934

Once the frontend has been fully migrated to the new (v2) api, we need to tear down the infrastructure that supports the old API:

• Review service logs for APIv1 to ensure it's not being used by any critical services
  • Work with CZII/Product to communicate the upcoming deprecation to any APIv1 users we can identify
• Disable any GitHub actions that deploy the APIv1
• Delete the happy stacks for APIv1 in staging and prod
• Wait a few days to ensure all systems are still working well
• Remove any happy configuration code from the cryoet-data-portal-backend repository
• Remove any apiv1 code from the cryoet-data-portal-backend repository
  • remove apiv1 itself
  • remove references to the apiv1 database/app (e.g. the v1 db ingestion scripts, and references to them from workflows)

If the frontend has already been migrated to Argus at this point, we should tear down the happy infrastructure in our accounts entirely:

IMPORTANT!!: Our database servers are set up alongside the rest of our happy infrastructure, so we will probably need to do some interesting terraform-fu like using terraform state rm / terraform state import to separate our DB config and Happy configs. The infra team may have done this before so it's worth asking whether they have tips.

• Reach out to #help-infra to see if there are any concerns/steps we need to take to do this properly.
• Separate our database server terraform from Happy env configuration
• Remove the dev/staging happy infrastructure from our cryoet-infra repository. Review the TF plans to make sure they won't break our argus services, and apply the changes.
• Remove the prod happy infrastructure from our cryoet-infra repository