Fix for overflowing localInterval in SegmentCostCache.Bucket

[tejaswini-imply]

Combination of cachingCost balancer + all segmentGranularity + no interval not loading segments after ingestion

• Combination is creating Segments of ETERNITY Interval (start - Long.MIN_VALUE/2, end - Long.MAX_VALUE/2)
• Joint cost calculation of these segments in SegmentCostCache buckets is posing the problem as the buckets are designed in such a way to have bucket_interval_start < segment_interval_start.
• For cost calculation start and end interval of segments are converted considering bucket_interval_start = 0 by taking difference between segment_interval_end, bucket_interval_start and normalised with MILLIS_FACTOR (millis_in_day/ log2), as a result, segment end-time conversion difference is overflowing(Long value).
• The current PR accounts for this overflowing case as it normalises segment interval, bucket_interval_start with MILLIS_FACTOR first (since MILLIS_FACTOR is of order 10^8) and then takes the difference.

---

Key changed/added classes in this PR

• SegmentsCostCache.Bucket
• LoadRuleTest

---

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.
• 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]

LGTM.

[kfaraz]

Merging as CI failure is unrelated.