[FLINK-10935][ResourceManager] Implement KubeClient with Fabric8 Kubenetes clients

[chunhui-shi]

##What is the purpose of the change
As part of native kubernetes integration. Introduce client wrapper to access Kubernetes service.

##Brief change log

• _Implement KubeClient interface and actual implementation.
• _Add mock kube server which is derived from Fabric's mock implementation.
• _A unit tests of KubeClient.

##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, Yarn/Mesos, ZooKeeper: (no )
• The S3 file system connector: ( no )
  ##Documentation
• Does this pull request introduce a new feature? (yes)
• If yes, how is the feature documented? (the document will be introduced in later pull requests)

[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 354ff96 (Sat Aug 28 13:07:50 UTC 2021)

Warnings:

• 2 pom.xml files were touched: Check for build and licensing issues.
• 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

[chunhui-shi]

This is the second pull request coming after #7844.

[tillrohrmann]

There is a dependency convergence error. Please fix this error @chunhui-shi.

[tianchen92]

This PR is outdated, see #8659

[flinkbot]

CI report for commit 354ff96: FAILURE Build

[wangyang0918]

Close this PR since it is already supported for a long time.