fix: update pvc values usage in PersistentVolumeClaim

[zhekazuev]

Issue

Incorrect paths to models.persistence.pvc values in the PersistentVolumeClaim template cause PersistentVolumeClaim to generate an error and fail to start the pod.

Ref: #16

Changes:

• use correct path to pvc values - .Values.models.persistence.pvc;
• update some templates - use with instead of if for: annotations and storageClassName;
• improve range operator for accessModes - do not generate accessModes when value is empty.
• delete newline for labes and space traling {{- for that

How to check

# should not generate pvc template and not add the name of PVC in Deployment
helm template test charts/local-ai/ --set models.persistence.pvc.enabled=false

# should generate pvc template and add the name of PVC in Deployment
helm template test charts/local-ai/ --set models.persistence.pvc.enabled=true

[mudler]

thanks!