Revert "reject publishing actions with a retriable error code if (#17509)"

[kfaraz]

The retries can cause TaskLockbox.giant lock to be held for a very long time causing ingestion to fail.

---

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.

[kfaraz]

Upon reverting this change, the failures will start to recur.
I think we should do the retry either at the task level or at the task action level instead of retrying the transaction in IndexerSQLMetadataStorageCoordinator.

I will update this PR accordingly.

[kfaraz]

@cryptoe , I am thinking we should just merge this revert as is.
I am creating a separate patch for the final fix.
Having two separate PRs will make backports cleaner.

Please let me know what you think.

[cryptoe]

Yeah I think having separate fixes makes things easier. With the upcoming April 1st druid code freeze, we can choose to fix the root issue after the code freeze as well.

[kfaraz]

Merging this PR.