release-22.2: sql: add VIEWACTIVITY/VIEWACTIVITREDACTED permission for ranges_no_leases

[THardy98]

Backport 1/1 commits from #98535.

/cc @cockroachdb/release

---

Fixes: #98514

This change adds the VIEWACTIVITY and VIEWACTIVITYREDACTED permissions access to ranges_no_leases. This allows users to view range data, necessary to use popular console pages:

• databases page
• database details page
• database table page

Prior to this change, users with VIEWACTIVITY/VIEWACTIVITYREDACTED would not be able to view these pages (would show error notification).

Release note (bug fix): Allow users with
VIEWACTIVITY/VIEWACTIVITYREDACTED permissions to access ranges_no_leases table, necessary to view important console pages (databases, database details, and database table pages).

Release justification: Category 2: Bug fixes and low-risk updates to new functionality

[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 

[j82w]

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

[rafiss]

ty for the cleanup!

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

[THardy98]

tyfr :)