Move the parent helm chart from a branch to the master branch of vets-api

[patrick-black-oddball]

The parent helm chart for vets-api needs to be moved to the master branch of vets-api. The following considerations need to be address in making the move.

1. The parent helm chart needs to start being published to a helm registry (ECR or Github) - the long term plan is for the charts to publish to ECR, but temporary publishing to github is allowed if argoCD issue occur.
2. The environment charts (in the manifest repo) - need to be able to load the parent helm charts in it's dependencies (current the dependency load is from an http load over github pages)
3. The current argo CD process for deploying each vets-api environment must still work, but utilize the published/versioned parent helm chart. ( this will probably involve adding a registry registration to argoCD for whichever registry the parent helm chart is published to)

Acceptance Criteria

Generated by Zenhub AI

• [ ] Scenario: Move the parent helm chart from a branch to the master branch of vets-api
  • Given the parent helm chart is in a branch
  • When the chart is moved to the master branch of vets-api
  • Then the following considerations should be addressed:
    1. The parent helm chart is published to a helm registry (ECR or Github)
    2. The environment charts (in the manifest repo) can load the parent helm charts in its dependencies
    3. The current Argo CD process for deploying each vets-api environment still works, but utilizes the published/versioned parent helm chart