Move common configurations to TuningConfig

[liran-funaro]

Description

The goal of this PR is to reduce code duplications and redundant code.
It does not affect Druid's UX. Only the internal code structure.

• Move common methods that are used in HadoopTuningConfig and in AppenderatorConfig to TuningConfig
• Rename rowFlushBoundary in HadoopTuningConfig to maxRowsInMemory to match TuningConfig API
  • This was already defined as @JsonProperty("maxRowsInMemory"), but the method name did not match TuningConfig API

---

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

---

Key changed/added classes in this PR

• TuningConfig
• AppenderatorConfig
• HadoopTuningConfig

[Eshcar]

LGTM
All changes seem to improve code quality
can you just add a sentence (in the jira) explaining this is a preamble to a later PR that will add the I2 extension point

[clintropolis]

I don't seem to be able to retry the failing CI which looks like it was a flaky test.

[liran-funaro]

Thanks, @clintropolis.
I appreciate your help merging this PR.
Please also check out the follow-up PRs: #10593 and/or #10001.