Helm install with OCI artifact fails where pod throws ImagePullBackOff caused by a broken default image tag (9.17.0)

Please note that security bugs or issues should be reported to security@pgadmin.org.

Describe the bug

Helm install with OCI artifact fails where pod throws ImagePullBackOff caused by a broken default image tag (9.17.0)

To Reproduce

Steps to reproduce the behavior:

1. Go to https://github.com/pgadmin-org/pgadmin4/blob/master/pkg/helm/README.md to get information on how to install pgadmin4 on K8s
2. Run installation example: helm install mypgadmin4 oci://docker.io/dpage/pgadmin4-helm --set ingress.enabled=true
3. See the error:

❯ kubectl get pods
NAME                            READY   STATUS                  RESTARTS   AGE
...
pgadmin4-5f9b755859-f6p9n       0/1     Init:ImagePullBackOff   0          5m53s
❯ kubectl describe pgadmin4-5f9b755859-f6p9n
...
Events:
  Type     Reason                             Age                    From                                   Message
  ----     ------                             ----                   ----                                   -------
  Warning  FailedScheduling                   6m15s                  gke.io/optimize-utilization-scheduler  0/6 nodes are available: 1 Insufficient cpu, 6 Insufficient memory. no new claims to deallocate, preemption: 0/6 nodes are available: 6 No preemption victims found for incoming pod.
  Normal   LoadBalancerNegNotReady            6m15s (x2 over 6m15s)  neg-readiness-reflector                Waiting for pod to become healthy in at least one of the NEG(s): [k8s1-b20544b5-default-pgadmin4-80-6070fc67]
  Warning  FailedScheduling                   6m14s (x2 over 6m15s)  gke.io/optimize-utilization-scheduler  0/6 nodes are available: 1 Insufficient cpu, 1 node(s) had untolerated taint(s), 5 Insufficient memory. no new claims to deallocate, preemption: 0/6 nodes are available: 1 Preemption is not helpful for scheduling, 5 No preemption victims found for incoming pod.
  Normal   Scheduled                          6m8s                   gke.io/optimize-utilization-scheduler  Successfully assigned default/pgadmin4-5f9b755859-f6p9n to gk3-autopilot-cluster-1-pool-1-9484f93c-scdk
  Normal   SuccessfulAttachVolume             6m2s                   attachdetach-controller                AttachVolume.Attach succeeded for volume "pvc-d9af2448-1e98-45be-949a-f752c4b6cd48"
  Normal   LoadBalancerNegWithoutHealthCheck  5m46s                  neg-readiness-reflector                Pod is in NEG "Key{\"k8s1-b20544b5-default-pgadmin4-80-6070fc67\", zone: \"us-central1-f\"}". NEG is not attached to any BackendService with health checking. Marking condition "cloud.google.com/load-balancer-neg-ready" to True.
  Normal   Pulling                            2m52s (x5 over 5m53s)  kubelet                                Pulling image "docker.io/dpage/pgadmin4:9.17.0"
  Warning  Failed                             2m50s (x5 over 5m52s)  kubelet                                Failed to pull image "docker.io/dpage/pgadmin4:9.17.0": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/dpage/pgadmin4:9.17.0": failed to resolve reference "docker.io/dpage/pgadmin4:9.17.0": docker.io/dpage/pgadmin4:9.17.0: not found
  Warning  Failed                             2m50s (x5 over 5m52s)  kubelet                                Error: ErrImagePull
  Normal   BackOff                            45s (x21 over 5m51s)   kubelet                                Back-off pulling image "docker.io/dpage/pgadmin4:9.17.0"
  Warning  Failed                             45s (x21 over 5m51s)   kubelet                                Error: ImagePullBackOff

Expected behavior

Pod comes up and become ready without issues with a default helm chart

Error message

Provided above

Screenshots

N/A

Desktop (please complete the following information):

• OS: N/A
• pgAdmin version: 4
• Mode: N/A
• Browser (if running in server mode): N/A
• Package type: Container

Additional context

N/A

Start with the installation instructions in pkg/helm/README.md and the chart configuration used by the OCI installation example. Check where the default pgAdmin image tag is set and verify it resolves from Docker Hub. Done means a default Helm install creates a pod that pulls its image successfully and becomes ready.