Setting configuration.logLevel prevents default backup storage to be found

[SCHrodrigo]

What steps did you take and what happened:
I am installing velero via helm with terraform on a GKE cluster, but when setting configuration.logLevel to any value velero's pod doest not start up. Logs for each situation [here] (https://gist.github.com/SCHrodrigo/73f94b30a9dfa8c664c36f90d432935c).

What did you expect to happen:
Velero to install with logLevel set from Helm.

The output of the following commands will help us better understand what's going on:
[Helm values for success and failure] (https://gist.github.com/SCHrodrigo/42c5c1ee4b91fa16889977599a0673ee)
[pod's logs for success and failure] (https://gist.github.com/SCHrodrigo/73f94b30a9dfa8c664c36f90d432935c)

Anything else you would like to add:
I am using velero-plugin-for-gcp, so I am not sure if this only occurs when configuring for GCP.

Environment:

• helm version (use helm version):
  version.BuildInfo{Version:"v3.15.2", GitCommit:"1a500d5625419a524fdae4b33de351cc4f58ec35", GitTreeState:"clean", GoVersion:"go1.22.4"}
• helm chart version and app version (use helm list -n <YOUR NAMESPACE>):
  CHART velero-7.1.0 - APP VERSION 1.14.0
• Kubernetes version (use kubectl version):
  Client Version: v1.30.2
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.27.11-gke.1062004
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
  GoogleCloud
  GKE control plane: 1.27.11-gke.1062004
  GKE node: 1.26.15-gke.1158000
• OS (e.g. from /etc/os-release): macOS 14.5