[FLINK-17612][python][sql-client] add the parse logic of Python command line options to CliOptionsParser in SQL Client.

[WeiZhong94]

What is the purpose of the change

This pull request adds the parse logic of Python command line options to CliOptionsParser in SQL Client.

Brief change log

• Add the parse logic of Python command line options to CliOptionsParser in SQL Client.
• Append the Python configurations from CliOptions to Session Environment.

Verifying this change

This change can be verified as follows:

• Start a local standalone flink cluster.
• Prepare a sql client session environment file with python UDF declaration.
• Added test that validates that TaskInfo is transferred only once across recoveries
• Launch the sql client with command line option "-pyfs xxx.py", "xxx.py" is the path of the python file that defines the python UDF.
• The sql client should up without any exception.

NOTE: After adding the PyFlink e2e test, the changes in this PR will be automatically verified.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit a0ce130 (Mon May 11 09:50:43 UTC 2020)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!
• This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• ee1f95c Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run travis re-run the last Travis build
• @flinkbot run azure re-run the last Azure build

[dianfu]

Change to Failed to parse the Python command line options?

[dianfu]

could use the enrich method defined in Environment as following:
final Environment sessionEnvWithPythonConfiguration = Environment.enrich( sessionEnv, options.getPythonConfiguration().toMap(), Collections.emptyMap());

[WeiZhong94]

It seems the enrich() method of the ConfigurationEntry only accepts the configurations that start with "table.". As the python configurations all start with "python.", the enrich method does not work for python configurations.

[WeiZhong94]

@dianfu Thanks for your review! I have updated this PR.

[dianfu]

LGTM.