Fix JWT tokens appearing in task logs

[Eason09053360]

use repr=False prevents sensitive data from being accidentally exposed in development, testing, or production environment

closes: #62428

---

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 or {issue_number}.significant.rst, in airflow-core/newsfragments.

[pierrejeambrun]

We should probably fix the underlying cause which is 'why is the secret masker not masking the token'. Most chances are it's because the ExecuteTask is first redacted (unknown object nothing happens) and then serialized, therefore the jwt remains.

I asked more information on the related issue. I cannot reproduce on my end without more details.

Need more information

[ashb]

This JWT token should, I think, never appear in task logs, because the Task itself never gets the actual JWT? It's not passed down/on to the task subprocess.

[ashb]

Closing in favour of #62129