[FLINK-14175] [flink-connector-kinesis] Update KPL version to 0.13.1

[abhilashaseth]

This fixes awslabs/amazon-kinesis-producer#224.

• JIRA - https://issues.apache.org/jira/browse/FLINK-14175
• mvn clean package succeeds after this change
• The version upgrade has already been performed (hence tested) in Flink 1.10.0 as part of FLINK-12847.

What is the purpose of the change

This pull request upgrades the KPL version in flink-kinesis-connector to fix thread leak mentioned in ttps://github.com/awslabs/amazon-kinesis-producer/issues/224.

Brief change log

Update the KPL version from 0.12.9 to 0.13.1

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): (yes)
• 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? (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 68f395d (Wed Dec 04 14:46:56 UTC 2019)

Warnings:

• 1 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.
  • Approved by @tweise [committer]
• ✅ 2. There is [consensus] that the contribution should go into to Flink.
  • Approved by @tweise [committer]
• ❓ 3. Needs [attention] from.
• ✅ 4. The change fits into the overall [architecture].
  • Approved by @tweise [committer]
• ✅ 5. Overall code [quality] is good.
  • Approved by @tweise [committer]

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:

• 68f395d : SUCCESS Build

Bot commands

The @flinkbot bot supports the following commands:

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

[tweise]

@flinkbot approve all