[native] Support system tables

[arhimondr]

Description

Querying system tables with native execution enabled may result in incorrect result.

Motivation and Context

Native and Java based executions have different partitioning functions implementation hence queries such the one below may return incorrect result.

SELECT *
FROM  (SELECT DISTINCT regionkey FROM table) t 
INNER JOIN  (SELECT regionkey FROM table$partitions) p 
ON t.regionkey = p.regionkey

Impact

Incorrect results returned when querying system tables with native execution enabled

Test Plan

Integration test

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

If release note is NOT required, use:

== NO RELEASE NOTE ==

[arhimondr]

The idea is to insert an extra "GATHER" exchange right on top of a TableScan of a system table. This will ensure partitioning function is applied by native worker consistently.

[mbasmanova]

@arhimondr Thank you, Andrii, for enabling queries that use system tables on Prestissimo and Presto-on-Spark on Velox.

[arhimondr]

@mbasmanova Happy to help

Presto on Spark (even with Java execution) is not supported though for a different reason. In Presto on Spark a distributed stage cannot read from a coordinator stage. Queries that require a system table to be read by a distributed stage (such as join) are not supported.