modalDialog: show dialogs on monitor with the mouse pointer

Show the dialog on the monitor containing the pointer, rather than
the monitor with active focused window. This brings it inline with
the behaviour seen when launching applications.

Remove the focusMonitor/focusIndex from LayoutManager. These
properties were only used by the modal dialogs. Remove them since
they are not being used elsewhere.

https://bugzilla.gnome.org/show_bug.cgi?id=642591
Updated Russian translation
Updated Greek translation
data: Actually substitute @GETTEXT_PACKAGE@ in schema files

https://bugzilla.gnome.org/show_bug.cgi?id=677497
extensionSystem: Initialize the HTTP session after parse time

We really shouldn't be creating GObjects while we're still parsing other
files for performance and clarity reasons.
Revert "extensionSystem: Initialize the HTTP session after parse time"

This reverts commit df5298d59c2c7b79c7477ecd1a9cf2dfa25e3b59.
extensionSystem: Initialize the HTTP session after parse time

We really shouldn't be creating GObjects while we're still parsing other
files for performance and clarity reasons.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
js: Remove unnecessary versions of clutter_actor_get_children

clutter_actor_get_children requires making a temporary GSList from
a linked list structure, and then creating a JS Array from that GSList.
For simple cases like the number of children, use clutter_actor_get_n_children.

https://bugzilla.gnome.org/show_bug.cgi?id=677426
appDisplay: Don't show apps in NoDisplay categories in the All view

We explicitly include NoDisplay applications in the ShellAppSystem because
we want app tracking for them, but we explicitly filter NoDisplay applications
out when showing them to the user because we don't want to show them to the
user. We also based our "All" apps view on a flattened list of apps. While
we did check for NoDisplay on the app item itself, we didn't check against
its parents. Refactor the app display view to not use a separate flat list
of applications, but instead a concatenation of all the applications in all
the loaded categories.

https://bugzilla.gnome.org/show_bug.cgi?id=658176
Fix name for the schemas file
Updated Norwegian bokmål translation
Updated Lithuanian translation
st: Trigger theme updates on resolution changes

Commit de8a66d4ce5 removed our own DPI handling for the one found
it Clutter, but broke resolution updates at runtime (for instance
when setting the "Large Text" option in Universal Access).

https://bugzilla.gnome.org/show_bug.cgi?id=677975
extensionSystem: Split off the extension downloader into a separate file

This keeps all UI out of the extension system, leaving it strictly for
loading and unloading extensions.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionUtils: Don't write to the filesystem on start

Create the potentially empty directory when we need to, not when we
don't.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionUtils: Remove version check for js-version

This is seldomly used, and isn't checked in SweetTooth. Just remove
this inconsistency here rather than adding infrastructure to manage
and check it elsewhere.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionUtils: Remove userExtensionsDir

Make this less stateful

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionUtils: Use signals rather than callbacks for finding extensions

This allows us to move to a file-monitor based approach in the future.

Since we need signals, we convert the current set of functions to an
object we attach signals too, leading to the new ExtensionFinder object.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionUtils: Create and load the extension object when scanning

This reduces some duplicate code when loading extensions.

https://bugzilla.gnome.org/show_bug.cgi?id=677586
extensionSystem: Load/unload stylesheets on enable/disable

I'm not entirely sure why this wasn't caught earlier.

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