allow expression "best effort" type determination to better handle mixed type arrays

[clintropolis]

Description

This PR fixes issues that can happen during ingestion of 'auto' typed columns which receive input with mixed type arrays; Druid ARRAY types only support all elements of the same type. The ARRAY "best effort" code has been modified to use the "least restrictive" logic that is now also used by default for the computed SQL schema, allowing things like [["a", "b", "c"], {"x": 123}] to now be handled as ARRAY<COMPLEX<json>> rather than throwing an incompatible type exception.

---

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.