Fail query planning if a CLUSTERED BY column contains descending order

[abhishekrb19]

Before this change, queries will successfully plan if any CLUSTERED BY column contains a DESC order. MSQE will validate that after the plan is generated and throw an InsertCannotOrderByDescending fault. This deferred validation makes it hard for clients that rely on whether a query can be successfully planned or not.

Now with this change, the validation is pushed down to the planning stage as a sql validation step. So the query planning will fail with a ValidationException if an INSERT or REPLACE query contains one or more clustering columns with descending order.

Release note

The MSQ fault, InsertCannotOrderByDescending, is marked deprecated. An INSERT or REPLACE query containing a CLUSTERED BY expression cannot be in descending order. Druid's segment generation code only supports ascending order. A query ValidationException is thrown instead of the fault in this scenario.

---

Key changed/added classes in this PR

• DruidSqlParserUtils.java
• Removed InsertCannotOrderByDescendingFault.java
• Adjust existing tests to use ASC instead of DESC; add new tests with DESC where the thrown exception is validated.

---

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.

[cryptoe]

LGTM. Thanks @abhishekrb19