fix: reduce log level for grpc claims

[tooptoop4]

fixes #9549

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

[jannfis]

I think we do not want to move the complete log statement to the debug level.

The linked issue complains about the group claims being logged when there are several dozens or even hundreds of groups in the JWT claim.

I think we have two options:

1. We could set logClaims to false in the caller if log level is lower than Debug
2. We could remove the groups from the claims in the logger method before marshaling it, if log level is lower than Debug

[crenshaw-dev]

Closing in favor of #9947