feat: strict tier-aware load/handoff status endpoints

[jtuglu1]

Description

Currently, Druid provides no way for handoff/loadstatus to track whether ≥ 1 segment replica exists in every tier a non-zero load rule exists for that segment's datasource. This provides a flag mechanism strictTierAwareSegmentLoad=true/false which scopes both handoff and loadstatus coordinator endpoints relative to this condition. This is particularly useful in the following cases:

1. You want to delay handoff of segments from realtime/batch tasks until the data is available in N > 1 distinct historical tiers to avoid data inconsistency issues between querying both tiers separately (e.g. data loading on a faster tier might surface the same data faster to queries before the slower tier).
2. You want to ensure high data availability (for example striping data across tiers mapped to specific AZs), and ensure that data is not surfaced to users until all AZ tiers have a copy.

Release note

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• 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.