Improved availability for zarf internal oci registry

[lsoica]

Currently, zarf internal registry is a single replica workload that pulls from itself.
In case of a multi node cluster:

1. If the registry pod gets rescheduled to a different node, it won't be able to pull its own image
2. If the underlying cluster is upgraded based on a node replacement strategy (e.g. eks), the registry pod gets rescheduled to a new node, hence, it won't be able to pull its own image

Describe the solution you'd like

The internal registry could be a multi replica (configurable) STS (from 1 to n, so that a consumer can pick the level of availability it need) and:

1. a service is created by the internal registry helm chart for each of the sts replicas, labeled so that zarf knows where to push
2. zarf pushes to every replica (to all the services that are properly labeled)
3. cluster nodes pull from any, through the nodeport

Backward compatibility is preserved by defaulting to replicaCount=1 for the internal registry STS.