release-23.1: server, ui: don't recommend drop index to unique indexes

[blathers-crl]

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

/cc @cockroachdb/release

---

Previously, when an index was not being used we were recommending it to be dropped, and only if the index was primary, we would not recommend.
We should not be recommending to drop unique indexes, because even when they are not used for read, they're important for inserts and being dropped would change the schema of the table.

Part Of #104143

https://www.loom.com/share/b4e7fae3594944d09ec9af7e53bed7be

Release note (ui change): No longer show drop index recommendation for unique indexes.

---

Release justification: small change improvement

[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 

[rharding6373]

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