release-22.2: opt: set default session settings and cache histograms in benchmarks

[mgartner]

Backport 3/4 commits from #93482.

Informs #98306.

/cc @cockroachdb/release

---

opt: set default session settings in micro-benchmarks

Setting the default session settings makes the micro-benchmarks more
representative of real-world workloads.

Epic: None

Release note: None

opt: cache histograms in test catalog

Histograms and histogram types are now cached in the test catalog. This
prevents computation and allocations made while building these
histograms from dominating profiles in optimizer micro-benchmarks.

Epic: None

Release note: None

opt: add benchmark for single-column table with histogram

Epic: None

Release note: None

Release justification: This is a test-only change. It prevents the optimizer
benchmarks from showing a huge regression between release-22.2 and
master because of the increase in the join re-ordering limit from 0 (i.e.,
join re-ordering disabled) to 8.

[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?

[mgartner]

I'm backporting this so that optimizer benchmarks don't show a huge regression between release-22.2 and master because of the increase in the join re-ordering limit from 0 (i.e., join re-ordering disabled) to 8.

[cockroach-teamcity]

This change is 

[DrewKimball]

Reviewed 2 of 2 files at r1, 1 of 1 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @mgartner and @michae2)

---

pkg/sql/opt/bench/bench_test.go line 597 at r1 (raw file):

	// Setup the default session settings.
	h.evalCtx.SessionData().ReorderJoinsLimit = opt.DefaultJoinOrderLimit

Probably doesn't matter, but this has the duplicate ReorderJoinsLimit

[mgartner]

pkg/sql/opt/bench/bench_test.go line 597 at r1 (raw file):

Previously, DrewKimball (Drew Kimball) wrote…

Probably doesn't matter, but this has the duplicate ReorderJoinsLimit

I'll fix this on master with #98310 but leave as-is here since it has no impact.