CLDYCON-7039: Add rbac.clusterRole.allowKubeProxy

[alexsouthard]

What does this PR do?

Adds a value to the helm chart which wraps the "nodes/proxy" permission to address an unaddressed vulnerability

Where should the reviewer start?

Should be relatively small, just a test on the helm chart install/node retrieval process

How should this be manually tested?

Must be using the helm chart to deploy

Any background context you want to provide?

Kubernetes has (at the time) said this is working as intended, so we need to add a fix

What picture best describes this PR (optional but encouraged)?

What are the relevant Github Issues?

Developer Done List

• Tests Added/Updated
• Updated README.md
• Verified backward compatible
• [] Verified database migrations will not be catastrophic
• Considered Security, Availability and Confidentiality

For the Reviewer:

By approving this PR, the reviewer acknowledges that they have checked all items in this done list.

Reviewer/Approval Done List

• Tests Pass Locally
• CI Build Passes
• Verified README.md is updated
• Verified changes are backward compatible
• Reviewed impact to Security, Availability and Confidentiality (if issue found, add comments and request changes)

[troy-chuang]

LGTM