Added core initialize message logic to the server

- Sends an initialize message after OnConnected is triggered to notify the client that it's ready for activity

#1889
Added the ability for connections to pre-buffer messages that are sent to them and then replay them.

- This will allow for people to send data in OnConnected

#1889

Conflicts:
	src/Microsoft.AspNet.SignalR.Client.JS/jquery.signalR.core.js
Added initialize logic to the common transports

- This way all transports utilize the same code path

#1889
Modified JS longPolling to utilize init message and cleaned

- Remove ping logic now that we support init message
- Also added the ability for the LongPolling transport to fail when a connection does not succeed

#1889

Conflicts:
	src/Microsoft.AspNet.SignalR.Client.JS/jquery.signalR.transports.longPolling.js
Changed how the rest of the transports trigger the onInitialize event

- They now trigger initialize when they receive an initialize message (handled in process messages within the common transports)

#1889

Conflicts:
	src/Microsoft.AspNet.SignalR.Client.JS/jquery.signalR.transports.serverSentEvents.js
Combined all JS changes into the minified versions
Expanded the QUnit Extensions library to support isTrue, isFalse, and comment

- This essentially makes the test assertion code easier to read and more consistent with XUnit type tests.
Added Functional and Unit tests to verify the init message functionality on the JS client
Fixed up old tests that expected LP to fail to now run successfully.

#1889
Modified all transports to no longer trigger their initialize function once they open.

- Instead they now trigger their initialize function once they receive an initialize message

#1889
Updated TransportHelper to unify all onInitialized logic.

- Triggers the onInitialized function once an initialize message is received

#1889
Added a ConnectingMessageBuffer to handle pre-connect data that is passed to the client

- If a user sends data in OnConnected or a user receives data prior to being fully "connected" we buffer the messages and then replay them once we've received the initialize message.
- This is all handled within the connection itself
- Also added the ConnectingMessageBuffer to all of the client projects

#1889
Added Functional and Unit tests to verify the init message functionality on the JS client

#1889
Addressed code review comments
Modified the drain command for the connecting message buffers to not return true or false

- Changed from tryDrain to drain
- For code review comments
Addressed code review comments

- Changed the init message parameter to S from Z
- Modified the tryInitialize function to not return a bool
Removed module from common testing project
Addressed code analysis issues
Merge branch '1889R' into release