[FLINK-16427][api] Remove directly throw ProgramInvocationExceptions in RemoteStreamEnvironment

[tisonkun]

What is the purpose of the change

This issue is a child issue of FLINK-15090.

With a previous discussion with @aljoscha we tend to reverse the dependency from flink-streaming-java to flink-client so that we have a semantic correct module dependency. That says, flink-streaming-java, just like flink-java(batch api), is an api module which should not know about the runtime.

This issue closes #11261 .

Brief change log

• Remove directly throw ProgramInvocationExceptions in RemoteStreamEnvironment

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

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): (yes, we possibly change the actual exception thrown from RemoteStreamEnvironment#execute, it is previously always ProgramInvocationException which is an unfortunately accident. We change the behavior for reverse the dependency from flink-streaming-java to flink-client in the future)
• 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)

cc @tillrohrmann

[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 c268d2b (Wed Mar 04 15:17:05 UTC 2020)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{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.

Details

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:

• b4770a7 Travis: 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

[aljoscha]

Manually merged! 👌

[tisonkun]

Thanks!