Release Candidate 0.3.0-0 - Create 0.3.0-0 edge artifacts with release-it

Description:

Create all Release Candidate 1 Artifacts with Release it Tag: 0.3.0-0

1. Use release-it to tag all EdgeOps repos with a new release candidate name. Naming structure for RC tags is 0.3.0-[sequential RC number]. Wait for all pipelines to release new tagged artifacts to the registry1 staging repo.
   1. npx release-it
   2. select preminor, yes to tag, yes to commit, yes to push
2. In the babu and edge controller Iron Bank repos:
   • Create new RC branches
   • Change STAGED_TAG to 0.3.0-[RC#] in hardening_manifest
   • Update tags in hardening_manifest to reflect the RC version, this should be handled by renovates tickets.
   • Create MRs to merge the RC branches to develop and assign to the Iron Bank team
   • Wait for Iron Bank to merge the branch to develop and publish new image tags to Iron Bank

Acceptance Criteria:

• 0.3.0-0 iso builder artifact available in s3
• 0.3.0-0 proxmox-provider available in registry1.dso.mil/edgeops-staging/proxmox-provider
• 0.3.0-0 edge-operator (helm chart) available in registry1.dso.mil/edgeops-staging/bigbangedge-controller
• 0.3.0-0 edgecompute-xr avaialbe in registry1.dso.mil/edgeops-staging/edgecompute-xr
• 0.3.0-0 edge-orchestrator available in registry1.dso.mil/ironbank/edge-orchestrator
• 0.3.0-0 bigbang-edge-controller available in registry1.dso.mil/ironbank/bigbang-edge-controller