Deprecate `native_execution_enabled` about presto

[shrinidhijoshi]

@shrinidhijoshi Shrinidhi, do you happen to know why 'native_execution_enabled' was added as a session property and not just config property. I'm starting to remember that it is somehow difficult to change config properties when launching PoS queries. Did we make this a session property to allow switching between PoS and PoS-on-Velox easily?

@mbasmanova Yes. That would be my best guess too. As at the time of PoC, internally at Meta, there wasn't any way to pass config props at invocation time for PoS queries.
Later however, we added a mode=NATIVE_EXECUTION option which we can use now, and deprecate this session prop.

Also, maybe all of these should change to config prop

    public static final String NATIVE_EXECUTION_ENABLED = "native_execution_enabled";
    public static final String NATIVE_EXECUTION_EXECUTABLE_PATH = "native_execution_executable_path";
    public static final String NATIVE_EXECUTION_PROGRAM_ARGUMENTS = "native_execution_program_arguments";
    public static final String NATIVE_EXECUTION_PROCESS_REUSE_ENABLED = "native_execution_process_reuse_enabled";
    public static final String NATIVE_DEBUG_VALIDATE_OUTPUT_FROM_OPERATORS = "native_debug_validate_output_from_operators";

[mbasmanova]

Outside of PoS, this session property is used in 3 optimizer rules

• PushPartialAggregationThroughExchange
• AddLocalExchanges
• AddExchanges

and SqlToRowExpressionTranslator.

None of these have direct access to FeaturesConfig (which is needed to fetch configuration property value).

All these rules are created in com/facebook/presto/sql/planner/PlanOptimizers.java which can inject FeaturesConfig and get access to the property. It can then pass the value to rule's constructors.

SqlToRowExpressionTranslator is called from many places and these places themselves do not have access to FeaturesConfig (e.g. StatementAnalyzer, QueryPlanner, etc.). It would require a good amount of plumbing to make this flag available.

@tdcmeehan @arhimondr Tim, Andrii, do you have any suggestion about how to best approach this?

[mbasmanova]

CC: @amitkdutta @spershin @gggrace14 @kewang1024 @pranjalssh

[mbasmanova]

@shrinidhijoshi Shrinidhi, do you happen to know why 'native_execution_enabled' was added as a session property and not just config property. I'm starting to remember that it is somehow difficult to change config properties when launching PoS queries. Did we make this a session property to allow switching between PoS and PoS-on-Velox easily?

CC: @arhimondr

[mbasmanova]

Possibly related issue: #20008