[FLINK-21903][docs-zh] Translate "Importing Flink into an IDE" page into Chinese

[xinggit]

What is the purpose of the change

The page url is https://ci.apache.org/projects/flink/flink-docs-release-1.12/zh/flinkDev/ide_setup.html
The markdown file is located in 'docs/content.zh/docs/flinkDev/ide_setup.md' now.

The doc is still in English on the master branch.So translate "Importing Flink into an IDE" page into Chinese

Brief change log

translate 'docs/content.zh/docs/flinkDev/ide_setup.md' file

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): 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? 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 426c888 (Fri May 28 09:11:22 UTC 2021)

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:

• 8863922 Azure: FAILURE

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

[xinggit]

cc @wuchong@xccui@klion26 . could you help to review this? thanks

[xinggit]

cc @wuchong Excuse me. I have resolved two conflicts for this merge request, please Could you help me review it as soon as possible, and then give me some comments

[wuchong]

Thanks @xinggit for the contribution, the translation looks good to me.

However, please DO NOT use git merge to fix conflicts, otherwise, comitters need to resolve the conflicts again when rebasing your branch. Please use git rebase to rebase your branch to latest master and fix conflicts. IntelliJ IDEA also provide an easy tool to do git rebase, you can find the tool via VCS -> Git -> Rebase.

[xinggit]

Thank you very much for your review and suggestion, but I'm sorry that I made a mistake and added a lot of commits.
I will open a new PR for the merge request