inspector: Bring the selector back

Make it a separate page instead of the old button path.
Updated POTFILES.in and POTFILES.skip
Updated Slovak translation
GtkColorSwatch: Avoid style context underflow

The last change accidentally removed the later restore, and
left the earlier, so we ended up with a restore-save sequence.
Thankfully, GtkStyleContext warns about this.
GtkSearchBar: don't peek out

When the searchbar is hidden, a 1-pixel-high piece of it is
still peeking out, because visible widgets are always allocated
at least 1x1. Work around this by setting child-visible to FALSE
in this situation.

https://bugzilla.gnome.org/show_bug.cgi?id=724096
GtkListBox: Support placeholders in ui files

This makes the gtk_list_box_set_placeholder functionality
available from GtkBuilder

https://bugzilla.gnome.org/show_bug.cgi?id=738111
viewport: Remove wrong save/restore
progressbar: Make the trough the default element

Gets rid of a bunch of save/restore calls and allows animating the
background (but not the slider, booo!)
switch: Set PRELIGHT state on widget
switch: Use trough style class by default

This allows animating the trough, and saves a save/restore pair.
stylecontext: Factor out a function
stylecontext: Don't cache the root values

Those are the ones that are special and get animated. Caching them only
causes confusion.
stylecontext: Move next pointer out of GtkStyleInfo

Instead, keep a GSList in the style context.
stylecontext: Make save/restore create a child CSS node

This is a change for how CSS is applied.

Previously, subelements (I'll take GtkEntry icons as an example) were
treated as having the same parent as the regular elements. So a selector
such as
  .entry
would match an entry inside a window. But it'd also match the icon image
inside the entry. So CSS like
  .entry { padding: 10px; }
would add 10px of padding to both the entry itself and to the icon image
inside the entry, so the icon would effective have 20px padding. To get
around that, one would have to unset it again like so:
  .entry { padding: 10px; }
  .entry.image { padding: unset; }
This is getting more and more of a problem as we make subelements
respect more properties that aren't inherited by default anyway, like
backgrounds and padding/margin/border.

This patch has one caveat though: It makes calling
gtk_style_context_save() the first time have an important side effect.
It's important to audit code to make sure it is only used for
subelements.

And last but not least, this patch is only useful if code unsets
parent's style classes that it doesn't want to apply any longer. Because
style classes are inherited by default (and I don't think we want to
change that), the example will still apply until the subelements no
longer contain the .entry style class.