sql: add telemetry counters for generic query plans

[mgartner]

Fixes #127651

Release note: None

[cockroach-teamcity]

This change is 

[DrewKimball]

Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @kyle-a-wong and @mgartner)

---

pkg/sql/plan_opt.go line 573 at r1 (raw file):

	switch opc.p.SessionData().PlanCacheMode {
	case sessiondatapb.PlanCacheModeForceCustom:
		telemetry.Inc(sqltelemetry.PlanTypeForceCustomCounter)

Do you think there could be any impact on performance potentially doing this for every query? Would it be worth doing only on a sampling basis or something?

[mgartner]

pkg/sql/plan_opt.go line 573 at r1 (raw file):

Previously, DrewKimball (Drew Kimball) wrote…

Do you think there could be any impact on performance potentially doing this for every query? Would it be worth doing only on a sampling basis or something?

I was worried about that, but we have other counters that are incremented for every query, so I thought this would be no different:

cockroach/pkg/sql/opt/exec/execbuilder/relational.go

Lines 2551 to 2552 in 2c32e20

	telemetry.Inc(sqltelemetry.JoinAlgoLookupUseCounter)
	telemetry.Inc(opt.JoinTypeToUseCounter(join.JoinType))

[mgartner]

TFTR!

bors r+

[craig]

Build succeeded:

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

[blathers-crl]

Based on the specified backports for this PR, I applied new labels to the following linked issue(s). Please adjust the labels as needed to match the branches actually affected by the issue(s), including adding any known older branches.

---

Issue #127651: branch-release-23.2, branch-release-24.1.

---

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

[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 7e10c1a to blathers/backport-release-23.2-127897: 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 23.2.x failed. See errors above.

---

error creating merge commit from 7e10c1a to blathers/backport-release-24.1-127897: 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.1.x failed. See errors above.

---

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