Add new compaction config and status APIs served by the Overlord

[kfaraz]

Changes

• Add new Overlord APIs to which allow reading and updating compaction status and configs
• If useSupervisors is true, the new APIs serve compaction supervisor-based information
  using the CompactionScheduleror the SupervisorManager
• If useSupervisors is false, the new APIs serve compaction config info using CoordinatorConfigManager
• Move some logic from CoordinatorCompactionConfigsResource to CoordinatorConfigManager
• Use CoordinatorConfigManager in OverlordCompactionResource to manipulate compaction configs
• Add CompactionSupervisorManager to act as a wrapper over SupervisorManager and allow
  manipulation of compaction supervisor specs
• Fix initialization bug in OverlordCompactionScheduler introduced in Use compaction dynamic config to enable compaction supervisors #17782

Cluster config payload

{
    "compactionTaskSlotRatio": 0.5,
    "maxCompactionTaskSlots": 1500,
    "compactionPolicy": {
        "type": "newestSegmentFirst",
        "priorityDatasource": "wikipedia"
    },
    "useSupervisors": true,
    "engine": "msq"
}

Release note

Add the following new Overlord APIs:

Method	Path /druid/indexer/v1/compaction	Description	Required Permission
GET	/config/cluster	Get the cluster-level compaction config	Read configs
POST	/config/cluster	Update the cluster-level compaction config	Write configs
GET	/config/datasources	Get the compaction configs for all datasources	Read datasource
GET	/config/datasources/{dataSource}	Get the compaction config of a single datasource	Read datasource
POST	/config/datasources/{dataSource}	Update the compaction config of a single datasource	Write datasource
GET	/status/datasources	Get the compaction status of all datasources	Read datasource
GET	/status/datasources/{dataSource}	Get the compaction status of a single datasource	Read datasource
POST	/status/datasources/{dataSource}	Update the compaction status of a single datasource	Write datasource

---

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.