Bump version to 5.32.79.0
[Application] Handle multiple attempts to terminate an application

Before this change multiple invokes of Application::Terminate() method broke
the app termination logic in case "OnSuspend" event handler was registered for
the app. Fixed now by introducing a dedicted "IsTerminating" check to
Application::Terminate() method.
Merge pull request #1542 from pozdnyakov/Avoid_app_double_termination

[Application] Handle multiple attempts to terminate an application
DEPS.xwalk: Roll ozone-wayland (0c4f175..d140a78).

d140a78 Dispatcher: Poll only for read notifications.
1b49869 Missing Changes: Return correct VSyncProvider.
37a9e2c Cleanup: Remove obsolete code related to frame callbacks.
2e2f1aa DisplayPollthread: Poll only for reading Wayland events.
0fcc8a5 Initial VSync support and ensure we flush Wayland display every
        frame.

This should help with the slow rendering issues that have been reported (I
couldn't find any JIRA issues about that though).
Merge pull request #1543 from rakuco/oz-wl-roll

DEPS.xwalk: Roll ozone-wayland (0c4f175..d140a78).
Bump version to 5.32.80.0
[Tizen] Display the top window when resume application from background.

For XPK applications with multipages, whenever a new page(window) is
created, it is saved as a root window inside current Crosswalk. In other
words, a list of root windows are created when running such kind application.

While Tizen app framework resumes the root window with stacking order
from bottommost(first) to topmost(last). As a result, the bottommost page is
showed when resume from background.

This PR provides only one root window per application, and all application
pages(windows) belong to this root window.

BUG = https://crosswalk-project.org/jira/browse/XWALK-900