Add new metric that quantifies how long batch ingest jobs waited for segment availability and whether or not that wait was successful

[capistrant]

Description

Supplement to #10676 and #11090 .... Adds a new metric that is emitted as a batch task completes it's wait for segment availability. The metric value is the milliseconds waited. The new dimension is a boolean that states if the wait was successful or not. The value of this metric is that it tells operators how long the coordinator is taking to distribute segments to historicals after indexing completes. As an operator myself, I track this value to make sure our coordinator performance is up to the expectation of users when it comes to how long after indexing completes their data is available.

---

Key changed/added classes in this PR

• AbstractBatchIndexTask
• IndexTaskTest

---

This PR has:

• been self-reviewed.
• 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 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.
• been tested in a test Druid cluster.

[kfaraz]

Thanks for adding this @capistrant, seems like a useful metric!

[a2l007]

+1 after CI

[capistrant]

Thanks for the review, @kfaraz and @a2l007 .. This metric has come in handy for my clusters as I work to make sure coordination is staying performant. I hope others find it useful as well