VSO helm test does not take into account the service account

**Describe the bug**
When launching the helm tests, they do not run as a service account with the proper credentials and they fail with :
```
{"level":"info","ts":"2023-11-28T23:43:56Z","logger":"initCachingClientFactory","msg":"Initializing the CachingClientFactory"}
2023-11-28T23:43:56Z ERROR setup Failed to setup the Vault ClientFactory {"error": "secrets is forbidden: User \"system:serviceaccount::default\" cannot create resource \"secrets\" in API group \"\" in the namespace \"\""}
main.main
/home/runner/work/vault-secrets-operator/vault-secrets-operator/main.go:215
runtime.main
/opt/hostedtoolcache/go/1.21.3/x64/src/runtime/proc.go:267
```

**To Reproduce**
Steps to reproduce the behavior:
1. Launch a k3d cluster
2. install vault + vso

**Expected behavior**
Maybe the test should use the same SA that vso uses ?

Reproduce the failure with a k3d cluster, Vault, and VSO installed, then inspect the Helm test setup and compare its service account with the one used by VSO. Done means the Helm tests run under the intended service account and no longer fail with the forbidden secrets error.

Written by the indexing model from the issue text.