release-23.1: cluster-ui: handle partial response errors on the database table page

[THardy98]

Backport 1/1 commits from #109521.

/cc @cockroachdb/release

---

Part of: #102386

Demos (Note: these demos show this same logic applied to both the databases and database details pages as well):
DB-Console

• https://www.loom.com/share/5108dd655ad342f28323e72eaf68219c
• https://www.loom.com/share/1973383dacd7494a84e10bf39e5b85a3

This change applies the same error handling ideas from #109245 to the
database table page, enabling non-admin users to use the database table
page and providing better transparency to data fetching issues.

unavailable fields provide a tooltip that displays the error impacting
that field.

Release note (ui change): Non-admin users are able to use the database
table page.

---

Release justification: UI improvement (regression fix)

[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 

[maryliag]

looks like you're getting some test failures

Reviewable status: complete! 0 of 0 LGTMs obtained

[THardy98]

looks like you're getting some test failures

Reviewable status: complete! 0 of 0 LGTMs obtained

Ah, it's because I forgot to backport #106778

opened a backport here: #110741

[maryliag]

Reviewable status: complete! 1 of 0 LGTMs obtained