[FLINK-13704][table-planner-blink] Re-add substr support in blink-planner to fix tpc-h e2e test failure

[JingsongLi]

What is the purpose of the change

substr is a common function, HIVE/SPARK/MYSQL/ORACLE/SQSERVER all support it. We should not delete it.
And tpc-h will generate the sql that contains substr. We should re-add it to fix e2e test failure.

Brief change log

Add substr in FlinkSqlOperatorTable, and add tests.

Verifying this change

ScalarFunctionsTest and SqlExpressionTest.
run the TPC-H E2E test.

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? no

[JingsongLi]

I have successfully run the TPC-H E2E test on my local computer.

[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 59abb0f (Fri Aug 23 10:17:29 UTC 2019)

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:

• 59abb0f : FAILURE Build

[wuchong]

LGTM. Thanks for the PR @JingsongLi .

It seems The failed YARN case is not related to this issue.

Will merge this.