ui: add column selector to transation page

[maryliag]

Add column selector to Transaction Page

Fixes #70148

Release justification: Category 4
Release note (ui change): Add column selector to transaction page

[cockroach-teamcity]

This change is 

[matthewtodd]

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

[Azhng]

Reviewed 2 of 11 files at r1.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @maryliag)

---

pkg/ui/workspaces/cluster-ui/src/statsTableUtil/statsTableUtil.tsx, line 41 at r1 (raw file):

  rowsRead: "Rows Read",
  statements: "Statements",
  statementsCount: "Statements",

statements and statementsCount have the same column label ?

---

pkg/ui/workspaces/cluster-ui/src/statsTableUtil/statsTableUtil.tsx, line 588 at r1 (raw file):

    );
  },
  statementsCount: (statType: StatisticType) => {

Do we also want to annotate the return types here like we did for other places in this PR ?

[maryliag]

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

---

pkg/ui/workspaces/cluster-ui/src/statsTableUtil/statsTableUtil.tsx, line 41 at r1 (raw file):

Previously, Azhng (Archer Zhang) wrote…

statements and statementsCount have the same column label ?

same column label, different tooltip. That's why they need to be different keys here

---

pkg/ui/workspaces/cluster-ui/src/statsTableUtil/statsTableUtil.tsx, line 588 at r1 (raw file):

Previously, Azhng (Archer Zhang) wrote…

Do we also want to annotate the return types here like we did for other places in this PR ?

the return type here is a little trickier, we're returning as Element, but is we add return type Element it requires several other parameters, so I made the decision of leaving those one as is

[Azhng]

Reviewable status: complete! 1 of 0 LGTMs obtained (and 1 stale) (waiting on @maryliag)

[maryliag]

bors r+

[craig]

Build succeeded:

• GitHub 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.

---

error creating merge commit from 662c466 to blathers/backport-release-21.2-70262: 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 21.2.x failed. See errors above.

---

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