fix: Prevent excessive segment assignment churn when using partial load rules

[capistrant]

Description

Add MOVE_TO matching profile segments to the list of matching in-flight loads so we account for moving segments in making replication decisions.

I am observing a cluster using partial loads and even after #19843 I am seeing what appears to be excessive replication churn. This seems to be a contributor

Release note

minor bugfix to how Druid accounts for partial segments who are actively being moved between historicals that will reduce unnecessary segment load churn.

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

---

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.