Switch to deploying an OGC process

[grallewellyn]

Right now this extension registers an algorithm, but we want to switch to the OGC process of deploying a process. The workflow for this would look like

1. User presses "Deploy Process" button from the UI. This should have information like:
   - Information about from where the run/ build commands are being run. Unclear if this is the current working directory where you ran the git clone or inside the code. These should be referred to as build and run scripts so that it is more clear
   - Info popup for Disk Space (GB) that explains if it is referring to the expected output or the code bade (entire git clone repo) as well
   - Overwrite existing process button that will do a PUT instead of a POST when deploying the process. User can only select this if a process with the same id and version already exists that was published by them or their group -> might not want an initial button for this, just a retry button
   - Deploy for individual user or deploy for group. There can exist an algorithm deployed by an individual user with the same id and version as an algorithm deployed for the group
   - Option to just build or build and deploy??
2. Runs Marjorie GitHub actions workflow, instructions to run here: https://github.com/MAAP-Project/ogc-app-pack-generator. This produces 2 products: - A CWL file
   - A Docker image published to our Google Container Registry
3. Calls POST https://api.dit.maap-project.org/api/ogc/processes (or PUT based on if user selected "overwrite existing process" from UI page in step 1)
4. Successfully deploys the process to HySDS and now users can submit jobs for this process