feat: add support for disable_local_ca_jwt in the Kubernetes auth method

[fad3t]

Follow-up of #972

---

Hi,

First of all thanks for developing this great project :)
I would like to propose my first contribution, about adding the support for the disable_local_ca_jwt in the Kubernetes auth method (cf. https://developer.hashicorp.com/vault/api-docs/auth/kubernetes#disable_local_ca_jwt).

This has been tested and it looks good; please let me know if anything else is needed/missing.

Thanks!
Fred

[fad3t]

@briantist I finally decided to start over this PR, hope that's fine for you :)

[codecov]

Codecov Report

Merging #997 (67d4d59) into main (31aca14) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

❗ Current head 67d4d59 differs from pull request most recent head 82419e8. Consider uploading reports for the commit 82419e8 to get more accurate results

@@            Coverage Diff             @@
##             main     #997      +/-   ##
==========================================
- Coverage   81.98%   81.87%   -0.11%     
==========================================
  Files          65       65              
  Lines        3019     2985      -34     
==========================================
- Hits         2475     2444      -31     
+ Misses        544      541       -3     

Impacted Files	Coverage Δ
hvac/api/auth_methods/kubernetes.py	89.36% <ø> (ø)
hvac/api/auth_methods/token.py	83.33% <100.00%> (ø)

... and 7 files with indirect coverage changes

[briantist]

Hi @fad3t , I'm sorry to report another major branch/workflow update in the hvac project, just as you've re-submitted this PR, but I think this will be the last!

The hvac project is simplifying its developer workflow and removing the develop branch. Please be aware for future PRs that the project's default branch is now main.

Since your PR was opened before this change, I have:

• updated your PR to merge into the project's main branch
• rebased your branch against main and force-pushed it (please pull before making any further changes)

At least this time there's no painful interactive rebasing ;) I believe the changes I made are all that needs to be done.

[briantist]

Thanks very much for submitting this and adding tests!

[fad3t]

Thank you @briantist !

[fad3t]

@briantist any idea when 1.2.0 will be released?

[briantist]

@fad3t it's close, I hope to get back to wrapping up v1.2.0 soon. I was away for several weeks, so now I have a lot of catching up to do, but it was already close when I left. I am also waiting for reviews from other maintainers on a few things. So I think it will be before the end of this month, but always hard to predict since it is all volunteer time. Thanks for your patience and thanks again for contributing!