http2: do the POST Upgrade dance properly
http2: fix EWOULDBLOCK in recv_callback()
http2: convert HEADER frames to HTTP1-like headers

... and then go through the "normal" HTTP engine.
http2: basic version of receiving DATA
http2: call it "HTTP 2" and not 2.0

The minor version will be dropped for HTTP 2 so it will make sense to
avoid using it in option names etc.
http2: Use nghttp2_session_mem_recv and nghttp2_session_upgrade
http2_recv: Return written length on CURLE_AGAIN
tests: Updated NTLM tests for NTLMv2 type-3 message
http2: add CRLF when first data arrives
http2: fix size check in on_data_chunk_recv
tests: Missed updating a type-3 message in commit 1c9aaa0bac
ntlm: Fixed a memory leak when using NTLM with a proxy server
netrc: Fixed a memory leak in an OOM condition
ftp: fixed a memory leak on wildcard error path
tests: make the authorization retry tests pass the torture tests
pipeline: Fixed a NULL pointer dereference on OOM
RELEASE-NOTES: Synced with 0f213fdca1
INSTALL: Corrected mentioned version number as release 7.34.1 became 7.35.0
winssl: improved default SSL/TLS protocol selection

For some reason Windows 7 SP1 chooses TLS 1.0 instead of TLS 1.2
if it is not explicitly enabled within grbitEnabledProtocols.

More information can be found on MSDN:
http://msdn.microsoft.com/library/windows/desktop/aa379810.aspx
runtests.pl: reverse line-ending conversion on Windows

It makes more sense to convert the expected output to [CR][LF] on
Windows than to force the actual, probably correct, output to [LF].

This way it is actually possible to see if curl outputs the correct
line-ending excepted by a text-aware test case.