release-22.1: sql: add metrics for prepared statement memory usage

[michae2]

Backport 1/1 commits from #97590.

/cc @cockroachdb/release

---

Add node-level metrics for memory used by prepared statements across all sessions.

Assists: #72581

Epic: None

Release note (ui change): Add the following new metrics to track memory usage of prepared statements in sessions:

• sql.mem.internal.session.prepared.current
• sql.mem.internal.session.prepared.max-avg
• sql.mem.internal.session.prepared.max-count
• sql.mem.internal.session.prepared.max-max
• sql.mem.internal.session.prepared.max-p50
• sql.mem.internal.session.prepared.max-p75
• sql.mem.internal.session.prepared.max-p90
• sql.mem.internal.session.prepared.max-p99
• sql.mem.internal.session.prepared.max-p99.9
• sql.mem.internal.session.prepared.max-p99.99
• sql.mem.internal.session.prepared.max-p99.999
• sql.mem.sql.session.prepared.current
• sql.mem.sql.session.prepared.max-avg
• sql.mem.sql.session.prepared.max-count
• sql.mem.sql.session.prepared.max-max
• sql.mem.sql.session.prepared.max-p50
• sql.mem.sql.session.prepared.max-p75
• sql.mem.sql.session.prepared.max-p90
• sql.mem.sql.session.prepared.max-p99
• sql.mem.sql.session.prepared.max-p99.9
• sql.mem.sql.session.prepared.max-p99.99
• sql.mem.sql.session.prepared.max-p99.999

---

Release justification: small change to metrics to improve observability.

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[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 

[yuzefovich]

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @DrewKimball and @rharding6373)

[michae2]

Failure looks unrelated so I'll go ahead and merge.