sql: add explicit column family assignments to persisted stats upgrades

[ericharmeling]

Fixes #99270.
Part of #99260.

This commit adds explicit column family assignments to the computed column ADD COLUMN statements for
system.statement_statistics and system.transaction_statistics version upgrades.

Epic: none

Release note: None

[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 

[ericharmeling]

With #99587, the backport of this PR should fix #99260.

[j82w]

Reviewed all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @ericharmeling)

---

pkg/upgrade/upgrades/create_computed_indexes_sql_statistics.go line 155 at r1 (raw file):

`

const addP99LatencyComputedColTxnStats = `

Can the upgrade test validate the family? Trying to think of some way to test this.

[ericharmeling]

Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @j82w)

---

pkg/upgrade/upgrades/create_computed_indexes_sql_statistics.go line 155 at r1 (raw file):

Previously, j82w (Jake) wrote…

Can the upgrade test validate the family? Trying to think of some way to test this.

I ran the systemschema roach test, which runs in the nightly (how this was caught in the first place). Here's the output (it passes now): systemschema_test_log.txt

Unfortunately, it looks like that's not caught by CI tests, which is how this didn't get caught in the first place.

So I've added another test validation function to TestCreateComputedIndexesOnSystemSQLStatistics that fails on master and succeeds on this branch.

[j82w]

Reviewed 1 of 1 files at r1, 3 of 3 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @ericharmeling)

[ericharmeling]

bors r+

[craig]

Build failed (retrying...):

• Bazel Essential CI (Cockroach)

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

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

---

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

---

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