queue2: only block serialized query when it's safe

We must be certain that we don't cause a deadlock when blocking the serialized
queries. One such deadlock can happen when we are buffering and downstream is
blocked in preroll and a serialized query arrives. Downstream will not unblock
(and allow our query to execute) until we complete buffering and buffering will
not complete until we can answer the query..

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=702840
pad: Don't consider flushing pads as needing reconfiguration

Renegotiation and reconfiguration will fail because all queries
and events won't be accepted by the pad if it's flushing. In the
best case this just causes unneeded work and spurious warnings in
the debug logs, in the worst case it causes elements to fail completely.
check: Added gst_check_setup_events_with_stream_id()

Added a new function gst_check_setup_events_with_stream_id(), since
gst_check_setup_events() does not work with multiple pads.

https://bugzilla.gnome.org/show_bug.cgi?id=703377
check: Change stream_id parameter name to match GtkDoc
tests: Remove funnel pad_alloc test
funnel: Use default pad function for upstream event/queries

The default functions in 1.x already do the right thing
funnel: Re-push all sticky events when buffers come from a different pad

Don't special case segment/caps, just push all sticky events when they are
received on the currently active pad or when the active pad changes.
gst-uninstalled: add new -bad mpegts lib

And remove signalprocessor/video libs from -bad which have gone
away or were merged into -base.
Add few missing allow-none annotation
baseparse: reset PTS after seek

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=702778
basesrc: Do not lock a mutex that does not exist

The GST_LIVE_LOCK is on GstBaseSrc, not on its source pad.
po: update POTFILES.in

https://bugzilla.gnome.org/show_bug.cgi?id=703682
allocator: fix type of gst_memory_alignment to match declaration

Fixes compiler warnings such as
gstallocator.c:61:8: error: conflicting types for 'gst_memory_alignment'
../gst/gstallocator.h:52:18: note: previous declaration of 'gst_memory_alignment' was here
inputselector: Keep previous active sinkpad around until we're done with it

Otherwise we'll send a new segment event downstream for each buffer.
bin: Always forward clock-lost message if we're not a top-level bin

This makes sure that no bin misses the clock-lost messages, independent
of the state, and could return an old, non-working clock from
gst_bin_provide_clock_func().

https://bugzilla.gnome.org/show_bug.cgi?id=701997
Update .po files
Release 1.1.2
Back to development
inputselector: Deactivate and remove pad without the inputselector lock

Otherwise we might get deadlocks caused by lock order inversion:
During the chain function the stream lock is first locked and then the
inputselector lock. During pad release we first locked the inputselector
lock and then deactivating the pad would lock the stream lock.

There's no reason why the inputselector lock should be required while
deactivating and removing the pad, it's only needed before.

https://bugzilla.gnome.org/show_bug.cgi?id=704002
basesrc: Leave the loop function faster if we're flushing

Especially don't even try to send stream-start event or try
to negotiate.

https://bugzilla.gnome.org/show_bug.cgi?id=704100