fix: /var/local paths should be under release name

[Abhinandan-Purkait]

Description

Currently we use /var/local/io-engine and /var/local/local-pv-hostpath/{{ .Release.Name }}
This is a bit too spread we should bundle it all within a common /var/local/{{ .Release.Name }} example:-
/var/local/{{ .Release.Name }}/{io-engine, localpv-hostpath}

This PR changes the helm chart to include this.

Motivation and Context

Regression

No

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added unit tests to cover my changes.

[niladrih]

“What's in a {{ .Release.Name }}? That which we call a rose by any other name would smell just as sweet.” - William Shakespeare

[Abhinandan-Purkait]

bors merge

[bors]

This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried.

Additional information:

Response status code: 422
{"message":"All comments must be resolved.","documentation_url":"https://docs.github.com/articles/about-protected-branches"}

[Abhinandan-Purkait]

bors merge

[bors]

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• continuous-integration/jenkins/branch