[FLINK-18173][build] Bundle flink-csv and flink-json jars in lib

[JingsongLi]

What is the purpose of the change

The biggest problem for distributions I see is the variety of problems caused by users' lack of format dependency.
These three formats are very small and no third party dependence, and they are widely used by table users. We can just bundle them in "flink/lib/".
It not solve all problems and it is independent of "fat" and "slim". But also improve usability.

Brief change log

Modify flink-dist to bundle jars.

Verifying this change

This change is a trivial rework 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): 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

[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 3c0eb22 (Mon Jun 08 11:56:32 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.

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:

• 892eed3 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

[wuchong]

Thanks for the contribution @JingsongLi . Could you remove the format jars from $END_TO_END_DIR/flink-sql-client-test/target/sql-jars, so that we can cover this by e2e tests.

[wuchong]

Not sure, but shall we use flink-csv-xxx-sql-jar.jar?

[JingsongLi]

I think we can respect module name.

[wuchong]

Shall we remove sql-jar since there is no difference between them so far, and it confuses users? cc @twalthr

[JingsongLi]

Considering that flink-avro also relies on Avro and Hadoop, if the user bundled Avro and Hadoop in the user's classloader, this may lead to the problem that the relevant dependency cannot be found in the parent classloader for flink-avro.

So flink-avro cannot be bundled into lib.

[wuchong]

LGTM.

[JingsongLi]

Thanks @wuchong for review, merging...