Let applications be chosen a few at a time

The catalog held fourteen applications. This machine runs thirty-four flatpaks,
so most of what is actually used had no way to be installed from here at all --
Zoom, Slack, Obsidian, Spotify, LibreOffice, OBS and its sixteen plugins.

So the catalog is seeded from the machine, and `panama apps` opens it: pick a
category, tick what you want, install just those. ./install still offers the
same catalog as whole categories, because during a first install you want coarse
and fast. Both read setup/lib/extras-catalog. Two parsers would eventually
disagree about what a category contains, and the one that disagreed quietly
would be the one that runs unattended.

Two pieces of syntax earn their keep. A `| Name` suffix gives the menu something
readable, since com.obsproject.Studio is not a name anybody wants to pick from a
list. An indented line belongs to the entry above it, which is how OBS carries
its plugins as one thing to tick rather than seventeen -- they are extensions of
the flatpak, useless alone.

That is also why creative moved from dnf to Flathub: the plugins attach only to
the flatpak, so the dnf build cannot have them. The rest of the category
followed rather than leave one machine with GIMP from dnf and its neighbour from
Flathub.

The contract now reads the catalog through the same parser instead of keeping a
third idea of the format, and checks the two things this syntax can break
silently: a label leaking into an install command, and a bundle that installs
the application without its plugins. It caught a typo in the Pixelorama id on
the first run.

It also got slow enough to be worth fixing -- fifty-one names, each its own
network call. One bulk query per manager took it from minutes to four seconds.
That query needs `flatpak remote-ls --all`: without it, end-of-life applications
are hidden and read as missing, which reported yuzu as gone from Flathub when it
installs perfectly well.

Claude-Session: https://claude.ai/code/session_01Q84axqUE5inJhf5Jz9CFy1

setup/packages/extras/creative

@@ -1,7 +1,33 @@
-# Images, video and audio. All from dnf or RPM Fusion.
-gimp
+# Images, video and audio.
+#
+# Flatpaks rather than the dnf builds these used to name. That was not a
+# preference: OBS's plugins are published as Flathub extensions and attach only
+# to the flatpak, so the dnf build cannot have them at all. The rest follow so
+# one machine does not end up with GIMP from dnf and its neighbour from Flathub.
+flatpak:org.gimp.GIMP | GIMP
+flatpak:org.kde.kdenlive | Kdenlive
+flatpak:fr.handbrake.ghb | HandBrake
+flatpak:com.orama_interactive.Pixelorama | Pixelorama
+flatpak:org.gnome.gitlab.YaLTeR.VideoTrimmer | Video Trimmer
+flatpak:org.gnome.gThumb | gThumb
 
-# Video editing, screen capture, and transcoding what comes out of them.
-kdenlive
-obs-studio
-HandBrake
+# OBS and the plugins that make it usable for capture on Wayland. Ticking this
+# installs all of them: they are extensions of the OBS flatpak, useless on their
+# own, and choosing them one at a time is a menu nobody wants to read.
+flatpak:com.obsproject.Studio | OBS Studio
+    flatpak:com.obsproject.Studio.Plugin.AdvancedMasks
+    flatpak:com.obsproject.Studio.Plugin.BackgroundRemoval
+    flatpak:com.obsproject.Studio.Plugin.CompositeBlur
+    flatpak:com.obsproject.Studio.Plugin.DownstreamKeyer
+    flatpak:com.obsproject.Studio.Plugin.GStreamerVaapi
+    flatpak:com.obsproject.Studio.Plugin.Gstreamer
+    flatpak:com.obsproject.Studio.Plugin.InputOverlay
+    flatpak:com.obsproject.Studio.Plugin.MoveTransition
+    flatpak:com.obsproject.Studio.Plugin.OBSPWVideo
+    flatpak:com.obsproject.Studio.Plugin.OBSVkCapture
+    flatpak:com.obsproject.Studio.Plugin.PipeWireAudioCapture
+    flatpak:com.obsproject.Studio.Plugin.SceneSwitcher
+    flatpak:com.obsproject.Studio.Plugin.Shaderfilter
+    flatpak:com.obsproject.Studio.Plugin.SourceClone
+    flatpak:com.obsproject.Studio.Plugin.SourceRecord
+    flatpak:com.obsproject.Studio.Plugin.WaylandHotkeys