Revert "workspacesView/workspacesDisplay: Ignore emulated events"

In mutter, there are two types of scroll events: discrete scroll events
and continuous scroll events.

For discrete scroll events, mutter uses a fixed scroll distance
(DISCRETE_SCROLL_STEP = 10).
For continuous scroll events, the scroll distance is already included,
in the dx and dy values.
When a scroll event is emitted, mutter pushes two events for each
scroll event: an emulated one and a non-emulated one.

For discrete scroll events this means, an emulated scroll event with
the direction 'SMOOTH' is emitted and a non emulated scroll event with
one of the directions 'UP', DOWN', 'LEFT', 'RIGHT' is emitted.
For continuous scroll events this means, a non-emulated scroll event
with the direction 'SMOOTH' is emitted and under circumstances an
emulated scroll event with one of the directions 'UP', 'DOWN', 'LEFT',
'RIGHT' is emitted.
The circumstance here for this is that the total amount of scroll
distances is that the dx or dy value surpasses the DISCRETE_SCROLL_STEP
value.

This means that events with the direction 'UP', DOWN', 'LEFT' or
'RIGHT' are not handled twice which was the convern in [1], as 'SMOOTH'
events are already always ignored in the workspacesView ([2]).

The other concern in the commit message was, that events, while natural
scrolling is enabled, are not handled correctly due to an unknown
scroll direction.
Mutter doesn't account the inverse scrolling direction when having
natural scrolling enabled (See also check_notify_discrete_scroll () in
mutter), which is important and necessary for remote desktop clients,
as otherwise the natural scrolling behaviour could be effectively
eliminated by having natural scrolling enabled on both server and
client side.
The scrolling direction is therefore always determined by the client
(See also [3]).

With commit 499af2dd continuous
scrolling events are not considered any more although second events
('SMOOTH' events) are already sorted out, which has the effect that
scrolling in the overview was made impossible (broken).
Natural scrolling events also don't have an effect as described above,
which makes the commit superfluous.

Fix scrolling in the overview again by reverting this commit. As
described above, there are no downsides to this.

See also the comments in
GNOME/mutter#1614

[1]: GNOME/mutter#1614 (comment 1011796)
[2]: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/499af2dd812b6dbac81209ccede0b1b3719703ba/js/ui/workspacesView.js#L765
[3]: GNOME/gnome-remote-desktop!25 (comment 1003423)

This reverts commit 499af2dd.

Closes: GNOME/mutter#1614
11 jobs for !1602 with fix-scrolling-in-overview in 5 minutes and 34 seconds (queued for 1 second)
latest detached
Status Job ID Name Coverage
  Pre Review
passed #1110949
check_commit_log

00:01:09

passed #1110950
check-merge-request

00:01:18

 
  Prep
passed #1110951
build-fedora-container

00:00:30

 
  Review
passed #1110953
eslint

00:02:09

passed #1110954
eslint_mr

00:01:58

passed #1110952
js_check

00:01:32

passed #1110957
no_template_check

00:01:29

passed #1110956
potfile_check

00:00:49

 
  Build
passed #1110959
build

00:02:31

passed #1110961
flatpak
flatpak

00:01:40

 
  Test
passed #1110962
test

00:01:52