It was not possible to just run 'mvn spotless:check', but instead one needed to use the fully qualified name of the plugin, i.e., 'mvn com.diffplug.spotless:spotless-maven-plugin:check'.

This is due to 'force-shading'; this module is declared as a child of the flink-parent pom (i.e., the root pom of the project), but is not actually declaring that very module as it's parent.
This seems to throw of maven, which fails to retrieve the plugin information from the parent.

Note that this is just a band-aid; a proper fix would declare flink-parent as the parent of force-shading, but this is the easier fix.

The reformatting increases file length for some files.

Keeping them inline does not work with google-java-format.

This closes #14391

This closes #14204

Relevant version changes:

adoptopenjdk-11-hotspot: 11.0.7+10-2 --> 11.0.9+11.2-3
openjdk-8-jdk: 8u242-b08-0ubuntu3~16.04 --> 8u275-b01-0ubuntu1~16.04
docker.io: 18.09.7-0ubuntu1~16.04.5 --> 18.09.7-0ubuntu1~16.04.6

This reverts commit 4cc0e722.

This closes #13941.

[FLINK-19898][Kinesis][EFO] Ignore ReadTimeoutException from SubcribeToShard retry policy

This closes #13886.

This closes #13655

[tmpfix] Set CI log level to TRACE for 'org.apache.flink.connector.base.source.reader' to debug FLINK-19448

This closes #13128

This experimental change aims to make the watchdog more accurate by extending the monitoring from the output to log files produced by the tests.
In particular the S3 tests seem to produce no output while they are producing output to the log files.

The risk of this change is that a hanging test is still producing log output (e.g. the test is stuck in a retry-loop).

This closes #13125

This closes #12907

This closes #12708