restrict-applications-selector: Make rows not focusable

Closes #52

See merge request pwithnall/malcontent!146

Only the controls inside them should be focusable. This saves having to
press the tab key twice as much as needed.

The row to open the restrict applications dialogue remains focusable, as
it doesn’t contain an interactive widget. It’s essentially one big
button.

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

Helps: #52

The toggle switches remain focusable, but the rows should not be
focusable. Otherwise tabbing through the list involves two tabs per row.

The screen reader continues to work correctly with this MR applied: when
tabbing to a new switch, it reads out the label from the row, plus the
switch state.

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

Fixes: #52

main: Restore previous whitespace in string

See merge request pwithnall/malcontent!145

So that we don’t change the string for no reason,
invalidating all existing translations.

Fix some build system leftovers from the GTK 4 port

See merge request pwithnall/malcontent!144

An app which currently depends on malcontent-ui-0.pc or
MalcontentUi-0.gir will fail to compile or run, respectively, aganist
the GTK 4-ified version.

Bump the API version, which is used in both those names. This will also
(I think) allow the two versions of libmalcontent-ui to be
parallel-installed.

The libmalcontent-ui API exposes types from GTK 4 (not 3) and
libadwaita.

When validating the .ui files, we need to determine the path to GTK 4's
relaxng schema. Previously this was erroneously looked up in the prefix
of GTK 3, which malcontent otherwise doesn't depend on.

Define the GTK dependency once, and use that variable everywhere.

GTK4

See merge request pwithnall/malcontent!141

AdwPreferencesPage is intended to be used as the first widget
inside page. It has an AdwClamp and a scrolled window to handle
just that.

Putting it in the MctUserControls widget is undesired, because
it introduces an oddly positioned scrolled window in the parental
controls page of Initial Setup, and if we ever reintroduce this
widgetry in Settings, it would suffer from the same problem.

Remove AdwPreferencesPage from MctUserControls, and replace it
with a vertical box. Add an AdwPreferencesPage in malcontent-controls
to compensate for that.

Append myself as the author of the files I've meaninfully changed.

Use named colors, and reimplement the disabled slider with a CSS
grayscale filter.

Simply expanding this list is enough to let the AdwClamp of
the parent AdwPreferencesGroup center it.

Replace the manual scaling of the font size by a proper style
class, and center-align it vertically.

The first call to act_user_manager_list_users() may lazily load
and notify the 'is-loaded' property, in which case we end up
indirectly recursing into reload_users(). Because we recurse
*after* purging carousel items, the same user is added twice:
once in the leaf recursion call, and once again in the call that
notified the 'is-loaded' property.

A simple workaround to this is purging carousel items after the
call to act_user_manager_list_users().

Let GTK handle that as it sees fit.

We don't actually want the menu button to have the same size
of the popover, since the popover can grow pretty wide.

The CSS-based animation is incompatible with the layout machinery
of GTK4, and we can't easily reintroduce it without another major
surgery in the carousel code, so just drop it for now.

Now that the inner GtkStack has margins, it has an odd offset from
what we would expect. A better widget to use is the GtkRevealer,
which must cover the entire allocation, and therefore will always
produce the expected x offset.

GTK4 has no size-allocate signal anymore, but we can use a custom
layout manager to produce the same effect.

There are overlays inside overlays and that is not playing well
with event delivery - the main box is eating away clicks from the
userlist avatars.

Remove all that, and the extra overlays, and just leave one simple
overlay handling the whole widgetry.

This makes the carousel look more like what it used to.

No functional changes, just reindent the file.

And set the 'suggested-action' style class too. This makes the
button more inline with modern GNOME HIG.

This property is read-only in GTK4.

Instead of delete-event. Pretty straightforward, 1:1 port to this
new signal.

It doesn't exist anymore.

It doesn't exist anymore.

In GTK4, the replacement to accelerators like this are shortcut
controllers.

Add a global shortcut controller to the primary menu button, and
bind it to F10.

A pretty straightfoward port, and most importantly, this function
actually exists in GTK4 :)

Make it an AdwBin subclass. Purge all GtkContainer usage, and expose
GTK4-inspired API to add items to the carousel, and also to control
the internal GtkRevealer.

And add a setter to its internal child.