[Presto-on-Spark] Move DetachedNativeExecutionProcess from test to src

[shrinidhijoshi]

Currently DetachedNativeExecutionProcess class is defined in test folder as it was only being used for test execution. But now that we want to support Presto-on-Spark in localMode, we want to be able to talk to an already running CPP process during e2e query execution. Moving it out into src to enable this

Test plan (N/A)

• Ensure all current tests that use DetachedNativeExecutionProcess pass

== NO RELEASE NOTE ==

[miaoever]

should we remove the redundant check at https://github.com/prestodb/presto/blob/master/presto-native-execution/src/test/java/com/facebook/presto/spark/AbstractTestPrestoSparkQueries.java#L137 ?

[shrinidhijoshi]

Good catch @miaoever . Looks like there are a few things we can clean up as a part of this. Will update

[tanjialiang]

Not sure what line it is as that class is no longer there. But things have changed recently so we should double check. Thanks

[tanjialiang]

High level question: What is the setup for local mode and why do we need a detached process for local mode? Thanks!

[shrinidhijoshi]

@tanjialiang There 2 types of localMode

1. With standalone cpp process (on devserver)(This PR) - This is needed when you want to start the CPP process in debug mode with breakpoints.

2. With inbuilt cpp process (downloaded through fbpkg) mimicing production - This one is useful when you just want to debug the java side of the flow and do not care about setting up cpp instance on your devserver

[miaoever]

Looks good to me. Thanks for adding this @shrinidhijoshi

[shrinidhijoshi]

Resolved merge conflicts

[shrinidhijoshi]

Test failures are unrelated. I re-ran the tests on laptop and they pass

[mbasmanova]

@shrinidhijoshi Please, make sure all CI is green.

[shrinidhijoshi]

@mbasmanova Will do. Kicked off the failing tests again

[ajaygeorge]

LGTM