Curator 5.7.0 Upgrade

[razinbouzar]

Version bump of Curator from 5.3.0 to 5.7.0 due as as fix to CURATOR-696 being included in the new version.

Fixes #16411 in addition to reverting the change in #16425.

Description

This is a minor version bump of Curator.

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.

[razinbouzar]

@kfaraz do you mind reviewing this version bump of Curator? @asdf2014 perhaps you can take a look as well since you submitted the original PR to revert.

[kfaraz]

Thanks for keeping tabs on this, @razinbouzar !
I plan to take a look at this soon. Want to be sure if the other fix you did in #16528 would still be needed after this upgrade.

[gianm]

Tagging with 31.0.0 to ensure we don't release 31.0.0 with the older Curator 5.3. We did 30.0.0 with Curator 5.5 (see #16445) and would want to release 31.0.0 with either Curator 5.5 or 5.7.

[kfaraz]

Removing this from Druid 31 milestone.

It had been originally included to ensure that Druid 31 was not released with Curator 5.3.
But since both master and 31.0.0 branch are already on Curator 5.5, this is not needed anymore.

As for upgrade to 5.7, it would require further testing.