[pgadmin4] Helm test with --logs flag fails due to pod not found

[alexfernandezv]

Describe the bug
Pgadmin4 chart test pod has the annotation: helm.sh/hook-delete-policy: hook-succeeded, which causes the test pod deletion after a successful test execution. When helm test <release_name> --logs command is executed, helm tries to find pod logs, but fails because pgadmin-test-connection pod has already been deleted.

Version of Helm and Kubernetes:
Helm: version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.17.5"}
k8s: Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T21:04:39Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"w indows/amd64"} Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-19T15:39:43Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"l inux/amd64"}

Which chart:
pgadmin4

What happened:
Test pod not found when helm tries to retrieve logs after executing helm test --logs

What you expected to happen:
Command exits succesfully.

How to reproduce it (as minimally and precisely as possible):
Install a valid release of the pgadmin4 and execute helm test --logs with the logs flag.

I suggest the possibility of being able to set labels for the test pod, in values.yml. To bypass the issue as helm/helm#9098 seems not solved.

Thanks in advance! :)