Revert "SQL: Plan non-equijoin conditions as cross join followed by f…

[somu-imply]

…ilter. (#14978)"

This reverts commit 4f498e6.

The commit was creating an issue with the rule CoreRules.JOIN_EXTRACT_FILTER, The Introduction of this rule caused cases with non-equijoin to get into a situation where Calcite was not able to decipher rule dependencies correctly as the outputs might be slightly differing from one another. This would cause planning to throw an OOM at the broker. We are reverting this for now to unblock the master. An example case is

EXPLAIN PLAN FOR
select t1.s_int, t1.c 
from 
  (select * from test_unnest_test_sql_array CROSS JOIN unnest(a_int) as u(c)) t1 
inner join 
  (select * from test_unnest_test_sql_array CROSS JOIN unnest(a_int) as u(c)) t2
on t1.c=cast(t2.s_int as char) 
where t1.s_int in (0, 1, 2, 999) and t2.s_int in (0, 1, 2, 999)

Will add unit test cases to catch issues after adding the Join_extract_filter_rule in a followup

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.