fix: update azure tenantId casing

[akashsinghal]

Description

What this PR does / why we need it:

Previous PR introduced a new azurekeyvault field to encompass all cert + key operations. The casing of the values.yaml file changed from tenantId to tenantID which is inconsistent with other values.yaml. This change reverts this change back to tenantId. This should lead to AKS e2e tests to pass.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #

Type of change

Please delete options that are not relevant.

• 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 not work as expected)
• Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• Does the affected code have corresponding tests?
• Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have appropriate license header?

Post Merge Requirements

• MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.41%. Comparing base (73ef709) to head (6b4bf59).
Report is 8 commits behind head on staging.

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #1385      +/-   ##
===========================================
+ Coverage    65.31%   65.41%   +0.10%     
===========================================
  Files          105      107       +2     
  Lines         5458     5552      +94     
===========================================
+ Hits          3565     3632      +67     
- Misses        1535     1565      +30     
+ Partials       358      355       -3     

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

[susanshi]

is this casing consistent with ClientId?

[akashsinghal]

Yes this is consistent casing for the clientId in the values file. The existing tenantId under akvCertConfig also was the same casing. The CRD fields use a different casing of ID though but I thought we should remain consistent with other fields in values.yaml

[susanshi]

left a clarification for ClientId, not a blocker for this PR to fix the aks test.

[binbin-li]

lgtm, thanks for the fix