Add logging to reveal reason to persist the hydrants

[kaisun2000]

Fixes #16408 16408

Description

Add a line of logging to give a signal as why persist is going to be triggered next in the peon. This would be useful to tune the ingestion spec.

The possible reasons are:

• maxRowInMemory reached
• maxBytesInMemory reached
• nextFlush time reached

Currently only "IncreamentalPersist" code path has this logging. Here we added the logging for the rest code path when increamental persist is not enabled.

Fixed the bug ...

Renamed the class ...

Added a forbidden-apis entry ...

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.

[Pankaj260100]

The possible reasons are:
maxRowInMemory reached
maxBytesInMemory reached
nextFlush time reached

It also persist all the data to disk when the ingestion worker wants to publish the data to deep storage.