Add extra env vars to charts

[filintod]

Description

Add optional extra env vars list to allow adding custom environment variables to dapr control plane system.

Issue reference

Please reference the issue this PR will close: #7182

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Unit tests passing
• End-to-end tests passing
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
• Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
• Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c11465f) 64.53% compared to head (9878e75) 64.55%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7183      +/-   ##
==========================================
+ Coverage   64.53%   64.55%   +0.02%     
==========================================
  Files         225      225              
  Lines       21070    21070              
==========================================
+ Hits        13597    13602       +5     
+ Misses       6306     6303       -3     
+ Partials     1167     1165       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ItalyPaleAle]

Please update the Helm chart README too

[ItalyPaleAle]

Make this a dictionary of key->value

[filintod]

usually this is an array, at least in bitnami charts. I can see the benefit of using a dictionary, and thought about it, but that also includes adding a range to parse it into an array of dictionary in the template. I did not see env vars added in a chart in dapr that I looked for to follow so decided to follow bitnami's standard that is easier to implement.

I mentioned the format here #7182

[ItalyPaleAle]

We have other fields in the chart that allow setting annotations and are dictionaries.

Using an array allows doing things like referencing secrets. However secrets can't be mounted in the current Helm chart so it doesn't matter in this case.

Using a dictionary is a lot simpler to pass via --set in Helm too.

My .02.

[filintod]

annotations are dictionaries by default so it kind of make sense. true about --set but now helm also has --set-json that makes life easier for most of previous hard cases

[filintod]

I could add the dictionary. let me think of a way to not make it too bad/verbose in the template

[filintod]

@ItalyPaleAle could you do another check

[filintod]

@ItalyPaleAle could you take another look please

[artursouza]

cc @ItalyPaleAle