utils: make sure slow GST_READ_UINT* variants don't have unexpected side effects

Fixes unit test on systems where unaligned memory access is not possible.

https://bugzilla.gnome.org/show_bug.cgi?id=695599
gst-uninstalled: add gst-editing-serves to GI_TYPELIB_PATH

So pygi can find it.

https://bugzilla.gnome.org/show_bug.cgi?id=695937
gst-uninstalled: remove ffmpeg libs from dynamic linker paths

We link those libs into the plugin statically, or use external
system libs, but never the internal snapshot dynamically.
tests: fix spurious failure in test_collect collectpads test

pop() in collected callback.

There were three threads in the test cases that hanged: the test thread and two
threads that push buffers. Each thread push one buffer on one pad. There are
two pads in the collectpads so the second buffer will trigger the
collect-callback.

This is what happens when the hang occurs:

The first thread pushes a buffer and initializes a cookie to the value of a
counter in the collectpads object and waits on a cond for the counter to change
and for someone to consume the buffer (i.e. _pop() it).

The second thread pushes a buffer and calls the collected callback, which
signals the cond that the test thread is waiting for.

The test thread pops both buffers (without holding any lock). Each call to
_pop() increases the counter broadcasts the condition that the first thread is
now waiting for. It then joins both threads (hangs).

The first thread wakes up and returns, since its buffer has been consumed.

The second thread starts executing again. When the callback, called by the
second thread, has returned it initializes a cookie to the value of a counter,
which has already prematurely been increased by the test thread when it popped
the buffers, and wait's on a cond for the counter to change and for someone to
consume the buffer (i.e. _pop() it). Since the buffer has already been poped
and the counter has already been increased it will be stuck forever.

https://bugzilla.gnome.org/show_bug.cgi?id=685555
docs: fix typo in query function example in Plugin Writer's Guide

https://bugzilla.gnome.org/show_bug.cgi?id=696142
toc: some documentation updates
basesrc: Don't send error if negotiate fails because we are flushing

Negotiation may be aborted by a flush from another thread that need to
stop the task (i.e. seek). Check that case and silently pause the task.

https://bugzilla.gnome.org/show_bug.cgi?id=696357
caps: Fix gst_static_caps_get(GST_STATIC_CAPS_NONE)

https://bugzilla.gnome.org/show_bug.cgi?id=696435
caps: Add unit test for GST_CAPS_{ANY,NONE} and GST_STATIC_CAPS_{ANY,NONE}

https://bugzilla.gnome.org/show_bug.cgi?id=696435
Update docs for gst_pad_create_stream_id_printf()

To indicate that format strings should be alpha sortable.
porting: hopefully clarify a little
buffer: Add annotations and pygi friendly extraction function

API: gst_buffer_extract_dup
baseparse: more inter-timestamp tracking

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=691481
baseparse: reset next_pts upon SEGMENT event

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=691481
argb-controlbinding: fix messed up property setter

This was misassigning the control sources. It was also leaking the old values if
a control source would be replaced.
gst: Add new GstContext miniobject for sharing contexts in a pipeline
pad: Remove SEGMENT sticky events when flushing

When flushing, it is expected that upstream will send a SEGMENT
event afterwards.
This also avoids stray SEGMENT events from coming through after a
flush.
pwg: Fix example
Revert "pwg: Fix example"

This reverts commit 5d64f27d881274a40f0441bb8c5b3816fdfc5b9e.

*sigh*
childproxy: fix gir warning