[FLINK-10791][e2e] Provide end-to-end test for Kafka 0.11 connector

This changes some modules that had a _2.11 dependency but didn't expose
it in their module name to instead depend on the ${scala.binary.version}
dependency.

The main reason for this is to make the build self contained, before,
with the hard-dependency on 2.11, when buildig for 2.12 it would not be
clear where the dependency would come from because it is not created as
part of the build. This could lead to inconsistencies. For example, when
adding a new class in flink-runtime but not recompiling on 2.11 but only
on 2.12, the 2.12 tests would fail when using that new class because
they would use 2.11 dependencies that weren't rebuilt with the new
class.

We also don't build flink-scala-shell and flink-connector-kafka-0.8
because they don't work with Scala 2.12.

This also includes $PROFILE in dependency convergence check script. This
is in preparation for building with "-Dscala-212", where we hace to
exclude certain things.

We also exclude Kafka 0.8 from stages when building for Scala 2.12

And add Scala 2.12 to the release scripts

The flip6 build profile only runs the Flip-6 related test cases. Moreover,
all Flip-6 related test cases are excluded when not running the flip6 build
profile. This should reduce testing time when adding more and more Flip-6
test cases.

Include flink-test-utils-junit in all submodules to make the Category marker interfaces Flip6 and OldAndFlip6 available

This closes #4889.

Disable it in most modules.

This closes  #4221.

Use scala.binary.version as defined in the parent POM and remove the
script to swap scala version identifiers.

This closes #3800

This closes #2460.

Currently, every project in Flink has a hard (compile scope) dependency on the jsr305, slf4j, and log4j
artifacts. That way they are pulled into every fat jar, including user fat jars as soon as they refer to
a connector or library.

This commit changes the behavior in two ways:

  1. It removes the concrete logger dependencies from the root pom file. Instead, it adds them to the
     'flink-core' project. That way, all modules that refer to 'flink-core' will have those dependencies
     as well, but the projects that have 'flink-core' as provided (connectors, libraries, user programs,
     etc) will have those dependencies transitively as provided as well.

  2. The commit overrides the slf4j and jsr305 dependencies in the parents of 'flink-connectors',
     'flink-libraries', and 'flink-metrics' and sets the to 'provided'. That way all core projects
     pull the logger classes, but all projects that are not part of flink-dist (and rather bundled
     in fat jars) will not bundle these dependencies again.

The flink-dist puts the dependencies into the fat jar (slf4j, jsr305) or the lib folder (log4j).

This closes #2324

- add suffixes
- adapt change-scala-version script

This closes #1529.

[FLINK-3195] [examples] Consolidate batch examples into one project, unify batch and streaming examples under on parent project

0.10-SNAPSHOT continues on branch release-0.10

Closes #851

Removed Disclaimer file
Eliminated unnecessary incubating substrings
Bumped version to 0.9-SNAPSHOT

Replacing the EventCollector and the MemoryArchivist.

Finished EventCollector and adjusted ExecutionGraph and ExecutionVertex to register actors as listeners.

- update _config.yaml of integrated documentation
- quick check on the quickstarts / build instructions to match the latest release
- quickstart.sh scrips now point to the correct versions.