Keys: one table file for the device's help panel and the website's key tables (#72)

Every screen's keys are constant tables in lib/core/src/app_keys.h (52 of
them, each under an `// id: Title` comment). An App's help() picks the table
of the state it is in. site/tools/gen_dev_docs.py reads the same file and
writes site/data/keys.toml; the `keys` shortcode shows a screen's tables on
its guide page, and /guide/keys/ shows all of them.

The Site job fails when the data file is out of date or a page asks for a
table that doesn't exist, and now also runs when app_keys.h changes. A key
added to an App shows up on the website without anyone editing a page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

src/apps/system_app.cpp

@@ -1,3 +1,4 @@
+#include "app_keys.h"
 #include "system_app.h"
 
 #include <Arduino.h>
@@ -74,13 +75,9 @@ void SystemApp::onExit() {  // nothing is kept while it's closed (Q120)
 }
 
 void SystemApp::help(std::vector<KeyHelp>& out) const {
-    out.push_back({"Tab", "the next view"});
-    out.push_back({"Aa Tab", "the view before"});
-    if (view_ == View::Tasks) {
-        out.push_back({"; .", "scroll"});
-        out.push_back({"s", "sort: cpu, stack, name"});
-    }
-    if (view_ == View::System) out.push_back({"; .", "scroll"});
+    if (view_ == View::Tasks) keys::add(out, keys::kSystemTasks);
+    else if (view_ == View::System) keys::add(out, keys::kSystemSystem);
+    else keys::add(out, keys::kSystem);
 }
 
 const char* SystemApp::helpTitle() const {