Merge pull request #1 from mono/develop

Develop
Merge pull request #2 from mono/develop

Develop
Merge pull request #3 from mono/develop

Develop
Merge pull request #4 from mono/develop

Develop
Merge pull request #5 from mono/develop

Monthly Merge!
Merge pull request #6 from mono/develop

Get latest
Merge pull request #7 from mono/develop

September update
Revert "Components.Add(...) should not Initialize Components"

This reverts commit c1544bce033f1d0432bb3ef360aef1707af15976.
GameComponents.Add() and Initializing GameComponents

Solve https://github.com/mono/MonoGame/issues/2105
Related to
https://github.com/mono/MonoGame/commit/c1544bce033f1d0432bb3ef360aef1707af15976

This is closer to XNA behavior.
-Initialization of Components is postponed until the call to
base.Initialize(...).
-Components added inside the virtual Initialize(...) but after the call
to base.Initialize(...) need to be self initialized.
-Components added later are auto-initialized.
remove unnecessary return
GameFrameworkViewSource supports the Activated event from the CoreApplicationView class, but that's an old class, which the most recent template doesn't use anymore (https://github.com/mono/MonoGame/wiki/Windows-8-Project-Types). The reason that this event is important is to enable game custom protocol activation.
Removed what looked like an unnecessary effort to write a fake file just to get details on what we already had.

Also fixed sound clicking due to including the header in the sound data buffer
Fixed build for Android so that there are 0 errors, 0 warnings.
0 errors, 0 warnings for OUYA.
0 errors, 38 warnings for iOS.
Incorporated comments from @danzel.
0 errors, 0 warnings for Linux.
Mac OS with 0 errors, 4 warnings.
Fixes for 0 errors, 0 warnings on Windows(DX) and WindowsGL.
0 errors, 9 warnings for PSM. All warnings are developer-generated using #warning directive.