release-22.1: server: improve visibility of ranges that fail to move during decommissioning

[cameronnunez]

Backport for 2 commits, 1/1 from #76516 and 1/1 from #79157.

cc @cockroachdb/release

---

Fixes #76249. Informs #74158.

This patch makes it so that when a decommission is slow or stalls, the
descriptions of some "stuck" replicas are printed to the operator.

Release note (cli change): if decommissioning is slow or stalls, decommissioning
replicas are printed to the operator.

Release justification: low risk, high benefit changes to existing 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 

[knz]

@cameronnunez can you check what is failing in CI?

[cameronnunez]

looks like an unrelated test failed:

------- Stdout: -------
=== RUN   TestRefresh/needs_refresh,_no_change
    cache_test.go:162:
          Error Trace:  cache_test.go:623
                              cache_test.go:162
          Error:        Not equal:
                        expected: 1
                        actual  : 2
          Test:         TestRefresh/needs_refresh,_no_change
    --- FAIL: TestRefresh/needs_refresh,_no_change (0.00s)

[knz]

you can get this merged now