[FLINK-10119] [table] Add failure handlers for JsonRowDeserializationSchema

[Jiayi-Liao]

What is the purpose of the change

The program will throw runtime exceptions and exit if json messages cannot be parsed correctly, which doesn't make sense to developers because it's very normal for them to receive dirty data from the source.
Now we offer format.failure-handler to deal with this kind of json data.

1. "fail": the deserialization will throw an exception.
2. "ignore": the deserialization will return a null value, which will be ignored.
3. "error-field": An additional field will be added into the row to store error messages and the other fields will be null.

Brief change log

• Add format.failure-handler in JsonValidator and failureHandler in Json.
• Optimize JsonRowDeserializationSchema to deal with "error" data.
• Add unit tests.

Verifying this change

Unit tests.

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

[Jiayi-Liao]

I think the travis testing failure is not caused by this PR.

[flinkbot]

CI report:

• ecc09ff UNKNOWN

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build