Helm chart values enrichment - dynamodb registry related

[vponoikoait]

What would you like to be added:
Based on #4260 (comment)
We've more options available for cases where we've registry: dynamodb

dynamodb-table, dynamodb-region which would be nice for configuration, so if we've same account but different regions EKS, we will be able to easily point to specific dynamodb, so we'll have it shared for two clusters

Why is this needed:
Case when we've shared dynamodb tablebetween multiple EKS in different region
extraArgs should work now, but it's much less obvious to set it up in such a manner - making it obvious should help a lot
Thanks in advance

[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