kvflowcontrol: fix logging redaction for a few types

[pav-kv]

The strings inside SafeFormat() were not marked as safe, and caused the values being printed as redactable.

Part of #136526

[blathers-crl]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is 

[sumeerbhola]

Reviewed 1 of 2 files at r1, 2 of 2 files at r4, 1 of 1 files at r6, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @arjunmahishi, @kvoli, and @rafiss)

[pav-kv]

TFTRs!

bors r+

[craig]

Build succeeded:

• windows_build
• examples_orms
• local_roachtest_fips
• linux_amd64_build
• linux_arm64_build
• docker_image_amd64
• unit_tests
• check_generated_code
• macos_arm64_build
• lint
• linux_amd64_fips_build
• local_roachtest
• macos_amd64_build
• acceptance

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 205fb8e to blathers/backport-release-24.3-137699: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 24.3.x failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}