[FLINK-1923] [runtime] Replaces asynchronous logging with synchronous logging using grizzled-slf4j wrapper for Scala.

This closes #628

This closes #35

This closes #604

Fixes several minor issues
Requesting non-available data throws Exception
Python process shutodwn more reliable
Synchronization done via TCP

This closes #586

This closes #189

With this change, users can submit a Flink job to a YARN cluster without having a local client monitoring the Application Master or job. You can basically fire and forget a Flink job to YARN.
For supporting this, the ApplicationMaster can now monitor the status of a job and shutdown itself once it is in a terminal state.

The change also verifies that various ways of setting the parallelism on YARN are passed through the system correctly (per job, session).

There was a bug in YARN container creation which made the configuration values for the heap offset useless. This change fixes this error.

All mentioned features and bugs are covered by the flink-yarn-tests.

This closes #542

This closes #421

This closes #533

This closes #497

This closes #486

This closes #454

This closes #407.

This closes #393

Conflicts:
	flink-java/pom.xml
	flink-java/src/main/java/org/apache/flink/api/java/typeutils/runtime/KryoSerializer.java

Conflicts:
	flink-java/src/main/java/org/apache/flink/api/java/typeutils/TypeExtractor.java
	flink-java/src/main/java/org/apache/flink/api/java/typeutils/runtime/KryoSerializer.java

This closes #412

The ./tools/qa-check.sh tool allows developers to check for common errors before opening a pull request.
The qa-checks are designed to be easily extensible by further checks.

This closes #366

Also dumped the stable release version in the docs config

This closes #333

This closes #355

This closes #345

- users can now also deploy Flink on YARN for executing a single job.
- The flink-yarn project has been moved out of the flink-addons module
- the MiniYARNCluster is used for testing Flink on YARN
- There is now a (undocumented) Java interface Flink's YARN client, allowing users to manually control the Yarn session.
- ALL ports used by Flink when running on YARN are automatically determined. In the past users reported problems with blocked ports (YARN is telling the client the RPC address of the application master)
- The checks before deployment have been improved to give better error messages if the user is requesting too many resources for a YARN session

Updated NOTICE files
Updated inceptionYear in pom

  - Move sling JSON dependency to streaming connectors (prev streaming core)
  - Exclude YARN API from transitive mapreduce-core dependencies we use the dependency
    only for .mapred and .mapreduce interfaces
  - Remove some unnecessary dependencies (junit in java8)
  - Manage Kryo dependency
  - Cleanup minor POM warnings.

This closes #268

to HadoopFileSystem wrapper, which supports all subclasses of org.apache.hadoop.fs.FileSystem.
This allows us to let users use all file systems with support for HDFS.
The change has been tested with Tachyon, Google Cloud Storage Hadoop Adapter and HDFS.

The change also cleans up the Hadoop dependency exclusions.

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