Handle nulls in DruidCoordinator.getReplicationFactor

[adarshsanjeev]

This resolves an issue in master, which was caused due to the collision of some PRs. A null pointer exception occurs if the replicant information was not available in SegmentReplicationStatus in the Coordinator.

---

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.

[kfaraz]

Thanks for catching this, @adarshsanjeev !
Are there tests that verify this?

[adarshsanjeev]

@kfaraz I think org.apache.druid.testsEx.leadership.ITHighAvailabilityTest fails due to this

[kfaraz]

Could you add a couple of lines in the existing DruidCoordinatorTest so that coverage is handled?