Fix Akeyless JWT connection credential is not redacted

[gopidesupavan]

Why

Airflow's default secrets redaction does not treat a bare jwt extra key as sensitive. Akeyless JWT credentials stored in connection extra can therefore be returned unmasked via the API and UI, exposing reusable authentication credentials to users who can read connections.

What

Rename the Akeyless connection extra key from jwt to jwt_token in provider metadata and generated provider info so it matches Airflow's default sensitive-key substrings and is redacted by default.
providers/akeyless/provider.yaml

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[eladkal]

cc @baraka-akeyless