replace g_hash_table_destroy with _unref for server query

This is necessary to allow passing the query on to another thread, given
that the developer adds another reference. With the current destroy
thing this will not work.

https://bugzilla.gnome.org/show_bug.cgi?id=702793
Add/fix some annotations
[examples] Added SoupLogger to get example

Now, instead of printing the debug information
manually we use SoupLogger for this with the "-d"
flag.

https://bugzilla.gnome.org/show_bug.cgi?id=703231
[examples] "get" uses -o to save to a file

The "get" example is now able to handle a new "-o"
parameter specifying the path of a file in which
to write the received body of a "GET" operation.

If the file exists, it will be overwritten.

https://bugzilla.gnome.org/show_bug.cgi?id=703229
soup-session: Fix a crash when destroying a NULL unpause source

Closes: https://bugzilla.gnome.org/show_bug.cgi?id=703461
soup-session: Force cleanup of REMOTE_DISCONNECTED conns for sync sessions

get_connection() assumed that REMOTE_DISCONNECTED connections would get
implicitly cleaned up elsewhere in the code, which is true for async
sessions, but not sync ones. This could lead to connection exhaustion and
hence hangs.

Closes: https://bugzilla.gnome.org/show_bug.cgi?id=703463
2.43.4
build: use AM_CPPFLAGS rather than INCLUDES

to make automake 1.13 happy
build: use AC_CONFIG_AUX_DIR and update .gitignore

(Primarily to move automake 1.13's test-driver out of the top level so
that the tests/ subdir autocompletes correctly again.)
misc-test: add a test that preemptively cancelling a SoupRequest works

https://bugzilla.gnome.org/show_bug.cgi?id=637039
Rename SoupKnownStatusCode to SoupStatus

Rename SoupKnownStatusCode to SoupStatus (so that the type name
matches the enum values), and then, for backward-compatibility, add a
new SoupKnownStatusCode enum with equivalent values so that
introspection-using code that was doing "SoupKnownStatusCode.OK", etc,
will still work.

https://bugzilla.gnome.org/show_bug.cgi?id=684409
examples: port get to plain SoupSession
Use GProxyResolver for all proxy resolving

Finish up the GProxyResolver porting started in 2.42 by removing all
the non-GProxyResolver proxy code from SoupSocket and SoupConnection
and implementing SoupSession:proxy-uri in terms of
GSimpleProxyResolver. If the user adds a SoupProxyResolverDefault to
the session, just use its GProxyResolver directly instead. If the user
adds any other kind of SoupProxyURIResolver to the session, use the
new SoupProxyResolverWrapper, which is a GProxyResolver that
translates from SoupProxyURIResolver.

https://bugzilla.gnome.org/show_bug.cgi?id=680273
tld-parser.py: Force file io to use utf-8

This fixes an issue where the build would fail with a UnicodeDecodeError
when run in a non-utf8 locale (which is typical in build environments)
using Python 3.

https://bugzilla.gnome.org/show_bug.cgi?id=702534
soup-uri: fix URI scheme parsing

The URI grammar allows a scheme to have digits in it after the first
character, and doesn't allow [.+-] in the first character.

https://bugzilla.gnome.org/show_bug.cgi?id=703776
[soup-logger] On response, always print headers

SoupLogger won't print any information upon
response until the "got-body" or
"got-informational" signals are received. If the
response message has been cancelled or requeued
first, we miss the headers information, even when
we would have been already able to print it.

Now, upon response, if the logging has not yet
happened when the "finished" signal is triggered,
we do perform the logging then.

https://bugzilla.gnome.org/show_bug.cgi?id=703200
soup-session: Warn if [un]pausing messages from a sync session

It was never meant to work, and can lead to weird behaviour and crashes.
Also mention this more explicitly in the documentation for
soup_session_[un]pause_message().

Helps: https://bugzilla.gnome.org/show_bug.cgi?id=703461
2.43.5