Is your feature request related to a problem? Please describe.
Currently, when deploying in standalone mode using the Helm chart, the data PVC and log PVC share the same storageClass and size configuration.

Based on [pvc.yaml], it appears that there is currently no option to configure the StorageClass and size for data and logs separately.

This causes a significant issue with resource efficiency. For example, if I intend to deploy a RustFS standalone instance with a 3TB data capacity, the Helm chart forces the creation of a 3TB log PVC as well, resulting in a total allocation of 6TB.

I believe the Data and Log PVCs should be decoupled, as logs typically require significantly less storage than data.

Describe the solution you'd like
I would like to separate the configuration for data and logs so they can be defined independently.

Current Configuration:

storageclass:
  name: local-path
  size: 256Mi

Proposed Configuration: I propose refactoring the values to support distinct configurations:

dataStorageclass:
  name: local-path
  size: 256Mi

logStorageclass:
  name: local-path
  size: 256Mi

(Note: naming conventions can be adjusted to match the project's style)

Describe alternatives you've considered
I have reviewed the existing values.yaml and documentation but could not find a workaround to size them differently in standalone mode without modifying the chart templates.

Additional context
If this proposal sounds good to you, I would be happy to create a Pull Request to implement this change.

Please let me know if I am missing something or if there is a specific reason for the current design. Thank you!