Merge values.generic and values.kind to values.dev

[meain]

What does this PR change?

Folks were getting stuck when kratos.kratos.development was not enabled by default. Suggesting this by default and using the name dev should ideally help out this.

@techmaharaj ~We can rework the docs and replace all references for values.kind.yaml and values.generic.yaml to values.dev.yaml and drop any mention of switching on kratos.kratos.development.~ (see below)

Checklist

I confirm, that I have...

• [x] Read and followed the contributing guide in CONTRIBUTING.md
• [ ] Updated documentation on the Paralus docs site (if applicable)
• [ ] Updated CHANGELOG.md
• [ ] Ran helm-docs to update docs for chart (if values.yaml file was changed)

[meain]

I have made one more change, as of now we have values.dev-eks.yaml which is applicable for eks and values.dev-generic.yaml which is for all the other including kind. I think this probably is a better solution.

[techmaharaj]

So it's either values-dev-eks.yaml or values-dev-generic.yaml .

Do we still need the note about the https setup and enabling kratos.development as true (the one that we have after installation)?

Or would you rather want a note that reads some thing like "If you're installing this in a production environment, please use values.yaml and configure the values mentioned here as required."

[meain]

So it's either values-dev-eks.yaml or values-dev-generic.yaml .

Yup

Or would you rather want a note that reads some thing like "If you're installing this in a production environment, please use values.yaml and configure the values mentioned here as required."

This sounds good, lets add this in the docs.