MI workflow issues from testing are resolved and deployed into production

[heidimok]

Context

In Jan-April 2023, we release the first set of changes for a new maintenance interface workflow in order to help curators better keep track of all the change drafts related to a campaign, platform, and instrument over time. See epic: https://github.com/NASA-IMPACT/admg-backend/issues/270. The first release before/after are documented here. Things that we left out were consolidated into a new issue for the future here.

Problem

The updated workflow is sitting in the test environment not yet deployed. We don't want to deploy until curators have tested it because of the significant changes. However, keeping it in test is creating problems over time because issues in the current production are being reported that might not be relevant once we have these changes merged. Also there is end to end testing in this version but not the one currently in production.

Acceptance Criteria

• [x] Curators have tested out the MI changes in the test environment https://github.com/NASA-IMPACT/ADMG-project/issues/792
• [x] Curators have reported issues here
• [x] Issues relevant to the workflow changes have been created and address
• [x] The updated MI workflow has been deployed from test to staging and then production

  
  ### Tasks

• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/548
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/549
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/550
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/551
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/552
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/553
• [ ] https://github.com/NASA-IMPACT/admg-backend/issues/555

[Tammo-Feldmann]

@heidimok , just as a reminder. After confirming that we are ready to merge the new MI workflow into production, we will also want to add the playwright end to end tests to our actions in the deployment pipeline.

[heidimok]

Branch to work from: feature/canonical-mi-workflow

[smwingo]

two main things holding are #551 #552 then can have updated MI on staging - then curators play/test, then to prod.

[heidimok]

Sprint 3 update

• We merged and closed #552
• We merged #551 but after manual testing I would like to carry this into Sprint 4. Once closed, we can most into the final step to merge the dev branch into staging

Note for Sprint 4

• Rather than continue to make changes to dev (not using the new testing we have in staging), any further bugs related to the MI workflow will be reported and done from staging NOT dev to keep things in one place.
• We need to let curators know that if there is a blocking issue to report it (or just let Heidi know to help report it) so that we can prioritize the fix in staging.