Extract bos-settings to its own repo; add breadhelp; JSON-driven Hyprland config

bos-settings moves to git.breadway.dev/Breadway/bos-settings (full history
preserved via git-filter-repo) so its release cadence is decoupled from
BOS's own. breadhelp takes its place as this repo's workspace member: a
GTK4 onboarding/help center replacing the old bos-welcome/bos-keybinds
bash scripts with searchable guides, an interactive keybind viewer
(sourced from the new keybinds.toml, not parsed out of hyprland.lua or
hardcoded), a troubleshooting wizard with one-click fixes, and a proper
first-run tour. bos-netcheck extracts bos-welcome's network-check half,
which still needs to run every login independent of breadhelp's own
first-run gating.

hyprland.lua's keybinds/settings/monitors/autostart are now JSON-driven
(binds.json/settings.json/monitors.json/autostart.json) with every
loader pcall-wrapped and falling back to hardcoded defaults per field on
bad or missing config, so bread* apps (bos-settings' new editors, and
breadhelp's keybind viewer) can read/write this config without ever
being able to leave the compositor unable to start.

CI's package.yml now builds breadhelp instead of bos-settings on tag
push; bos-settings needs its own equivalent workflow in its new repo
(not yet set up).

src/services/breadd.rs

@@ -0,0 +1,16 @@
+//! Maps a `--suggest <id>` payload (sent by a breadd Lua module, e.g.
+//! `breadhelp-suggest.lua` reacting to `bread.monitor.connected`) to Home
+//! tab banner text.
+
+pub struct Suggestion {
+    pub text: String,
+}
+
+pub fn resolve(id: &str) -> Option<Suggestion> {
+    match id {
+        "monitor-setup" => Some(Suggestion {
+            text: "New monitor detected — want to set up your display layout?".to_string(),
+        }),
+        _ => None,
+    }
+}