Enable querying policy-enabled table in MSQ, and use RestrictedDataSource as a base in DataSourceAnalysis.

[cecemei]

Description

This PR enables querying policy-enabled table in MSQ.

---

Key changed/added classes in this PR

• DataSourceAnalysis, getBaseTableDataSource can now return the base of RestrictedDataSource. This is a more robust solution than using the underlying table as base.
• DruidQuery, can also be created by withPolicy, which just applies policy restriction to the original query.
• MSQTaskQueryMaker would apply restrictions on DruidQuery, instead of throw permission error.
• DataSourcePlan can handle RestrictedDataSource.
• a new class RestrictedInputNumberDataSource, which basically wraps a NumberDataSource with a policy, and its SegmentMapFn can be used to create a RestrictedSegment.
• RunWorkOrder, try to make a few refactors to make the code clear, no behavior change. ShufflePipelineBuilder.build(), it was not clear before that the channel future should only be returned when the resultFuture is ready. Also, the sanity check is moved to OutputChannels.
• BaseLeafFrameProcessorFactory.makeProcessors(). Previously, makeSegmentMapFnProcessor can return null. After this PR, it cannot. The difference is that now the SegmentMapFn from query.dataSource is handled in ChainedProcessorManager for all query (was just join query before).

---

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.