Refactor: Remove type params from MetadataStorageActionHandler

[kfaraz]

Description

The MetadataStorageActionHandler deals with persistence of Task and related objects.
But those model classes exist in indexing-service module which forces the MetadataStorageActionHandler
to handle generics unnecessarily. This makes the code cluttered and difficult to understand at times.

Changes

• Move MetadataStorageActionHandler and factory classes to indexing-service module
• Move implementations to respective extensions
• Simplify class TaskInfo by removing type parameters
• Add class TaskIdStatus
• Remove class TaskStuff
• Add DerbyTaskStorageModule to bind the MetadataStorageActionHandler to its default impl on CliOverlord
• Remove references to the tasklog table as it had been disabled in Remove task action audit logging and druid_taskLog metadata table #16309

Developer notes

The MetadataStorageActionHandler extension point is being updated to have simpler APIs.
This is a breaking change for any SQL metadata extensions in the wild.
The changes for PostgreSQL, MySQL and SQLServer are already handled in this PR.

---

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.

[jtuglu1]

LGTM – thanks!

[jtuglu1]

I'm assuming we don't want to perform validations on these fields?

[kfaraz]

Do you mean a null check?

[kfaraz]

Thanks for the reviews, @jtuglu1 , @gianm !