[FLINK-19569][table] Upgrade ICU4J to 67.1

[godfreyhe]

What is the purpose of the change

Upgrade ICU4J to 67.1 due to https://nvd.nist.gov/vuln/detail/CVE-2020-10531

Brief change log

• update icu4j to 67.1 in the pom and notice file

Verifying this change

This change is already covered by existing tests, such as PrintUtilsTest.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
• The serializers: (yes / no / don't know)
• The runtime per-record code paths (performance sensitive): (yes / no / don't know)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
• The S3 file system connector: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[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 fdb771f (Tue Oct 27 07:22:13 UTC 2020)

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.

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

[wuchong]

The version in flink-table-planner/pom.xml is not updated.

[godfreyhe]

The version in flink-table-planner/pom.xml is not updated.

Good catch

[wuchong]

Thanks for the updating. LGTM.

[godfreyhe]

@flinkbot run azure

[flinkbot]

CI report:

• 6ee7fc3 Azure: CANCELED Azure: FAILURE 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

[godfreyhe]

@flinkbot run azure

[godfreyhe]

Azure passed in https://dev.azure.com/godfreyhe/godfreyhe-flink/_build/results?buildId=38&view=results