Quality of life changes to the aws-efs-csi-driver helm chart.

[RadOctocode]

Is your feature request related to a problem?/Why is this needed
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I want to add some quality of life changes to the helm chart for the aws-efs-csi-driver. I have a patched version of these charts and would like to contribute the changes made.
/feature

Describe the solution you'd like in detail
A clear and concise description of what you want to happen.
I would like to include the following quality of life changes

• In node-daemonset.yaml
  • templatize priorityClassName
  • include pod labels
  • use values for hostNetwork
• In storageclass.yaml
  • add .metadata

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
the user could patch the chart each time before using it.
Additional context
Add any other context or screenshots about the feature request here.

[RadOctocode]

Here are my proposed changes

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten