feat: Server view improvements for historical detail (decommissioning, turbo segment loading, cloning)

[capistrant]

Description

Broken out from #19250 due to that PR getting too large and difficult to review. This PR focuses on just the services view where we add information in the "Detail" column that will help operators know about any special state that their historical services are in

In the image you can see there are new details for:

• DECOMMISSIONING
• TURBO SEGMENT LOADING
• cloning

The creating of this PR flagged a bug in CloneHistoricals.java. When going from N to 0 clone mappings; when N > 0, you end up not resetting the clone status manager and that means the api is inaccurately reporting clones when there are no mappings anymore. This PR fixes that issue. Note that the bug appears to be a reporting issue, the coordinator is not still treating the removed mappings as clones.

Release note

Enhance the services view in the web console by adding information to the "Detail" column for Historical services who are:

• cloning from another historical
• in turbo loading mode
• in decommissioning mode

---

Key changed/added classes in this PR

• CloneHistoricals

---

This PR has:

• been self-reviewed.
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.