Fix storage class name variable

[mrgionsi]

• Please check if the PR fulfills these requirements

• The branch naming convention follows our guidelines
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fixing

• What is the current behavior? (You can also link to an open issue here)

StorageClass name is not generated correctly due to wrong storageClassName value.

• What is the new behavior (if this is a feature change)?

The Helm Chart generate PVC templates using the correct StorageClassName from the values.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No

[imgios]

Nice one! Just checked also the pipeline build and it seems to be doing it right:

# Source: servarr/templates/pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: downloads-volume
  annotations:
    ...
spec:
  storageClassName: longhorn
...
---
# Source: servarr/templates/pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: media-volume
  annotations:
    ...
spec:
  storageClassName: longhorn
...
    requests:
      storage: 250Gi
---
# Source: servarr/templates/pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: torrent-config
  annotations:
    ...
spec:
  storageClassName: longhorn
...

This can be merged 👏🏻