[WIP] [native] Derive TableScan stream type as FIXED

[arhimondr]

Description

In native a fixed number of drivers is created for a pipeline containing TableScan

Motivation and Context

To avoid unnecessary local exchange when fixed number of streams is necessary (for example for TableWriteOperator)

Impact

Improved performance for certain type of INSERT INTO queries

Test Plan

CI, Unit Tests

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• 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.

== NO RELEASE NOTE ==

[facebook-github-bot]

@arhimondr has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[jaystarshot]

// Native execution creates a fixed number of drivers for TableScan pipelines

Is there a reason why only native execution creates fixed number of drivers?

[arhimondr]

In Presto (Java) the number of TableScan drivers created was chosen adaptively. That added a lot of complexity to TaskExecutor and the benefit was not clear.

In Velox the number of TableScan drivers is fixed. The adaptivity can still be achieved via delivering splits to only a subset of TableScan drivers without going into complexity of managing the number of drivers dynamically. Here's an example where @xiaoxmeng adds TableScan scaling: facebookincubator/velox#11879