Create a document that outlines the changes to be made in order to move swatch-metrics into quarkus.  There should then be a discussion with the team to review the plan prior to executing during SWATCH-676.

This is card is less about the curation of the document, and more about starting to sift through the code (maybe even a POC?) trying to gather a master TODO list.

Examples of things that I'm thinking of:

• are there any other database interactions that we didn't take care of as part of SWATCH-573?
• is there any/how much boilerplate code is going to need to be duplicated?
• same question about generated api clients (like the prometheus one?)
• which gradle subprojects will be dependencies?
• how bad will we be bitten by not using swatch-core?
  • swatch-metrics needs to be self-contained
• creation of a swatch-metrics quay repo, updating clowdapp to reflect the locations of new images
• unit test needs to port over too

There's a good possibility that the placeholder story for this (SWATCH-676) will need to be split into multiple stories.

DONE

• A doc exists that outlines the challenges of moving swatch-metrics to quarkus
• A meeting is scheduled with the team to review the doc

Note: No actual testing to be done yet, but design doc should be reviewed by QE