release-23.1: server, ui: more search criteria options on SQL Activity

[blathers-crl]

Backport 1/1 commits from #103984 on behalf of @maryliag.

/cc @cockroachdb/release

---

Fixes #101817

More Options were added on Search Criteria for SQL Activity page.
For top limit: 1000, 5000 and 10000.

For Priority By On Statements page:

• Last Execution Time
• Max Latency
• Max Memory
• Min Latency
• Network
• P50 Latency
• P90 Latency
• Retries
• Rows Processed

For Priority By on Transactions page:

• Max Memory
• Network
• Retries
• Rows Processed

It also fixes the sort on CPU that was sorting by the wrong column.

Release note (ui change): On SQL Activity page add more Search Criteria options, by adding for "Top": 1000, 5000 and 10000. For "By" on Statements tab: - Last Execution Time, Max Latency, Max Memory, Min Latency, Network, P50 Latency, P90 Latency, Retries, Rows Processed.
For "By" on Transactions tab: Max Memory, Network, Retries, Rows Processed.
Release note (bug fix): Uses the correct column to sort by on CPU.

---

Release justification: improvements to fix regression

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

[cockroach-teamcity]

This change is 

[kevin-v-ngo]

This is great! FYI @dongniwang

@maryliag, can we add the 'None' option if it's not added already? It should be in figma and called out in the issue. TOP would be disabled.

This would help solve the problem that users have when looking for a specific query - they don't need to go through all the options and do the search.

[maryliag]

This is a backport, so any new changes will be on a different PR. So for the "None" I didn't add it, because we always use one sort, and the default is by latency (which is what we were doing previously), so could be confusing a None that is actually doing a sort. We can discuss it offline

[j82w]

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