Let the install set how many steps a run may take

The two limits were compiled in: a task run stopped at
AppData.HarnessMaxToolSteps (200) and a chat reply at
AppData.BotReplyMaxToolSteps (8), so an install that needed a longer task
had to rebuild.

Both are now `app_settings` rows (`harness_max_tool_steps` and
`bot_reply_max_tool_steps`), read at the two loop call sites through
grabHarnessMaxToolSteps and grabReplyMaxToolSteps, and edited by the super
admin on Settings > General beside the prompt appendix. Zero clears a
limit back to the code default, like the bot file quota.

readStepLimit keeps the saved number only when it is a whole number of at
least 1 and no more than AppData.BotStepLimitMax (1000), so a blank, a
zero or a typo falls back instead of stopping every run before its first
turn, and a huge number still ends in the wrap-up report.

runTextLoop keeps AppData.HarnessMaxToolSteps as its default, so it stays
free of database reads and its tests run as they did.

src/types/index.ts

@@ -1192,6 +1192,17 @@ export type PagePropsType = {
         setting_key: string;
         text: string;
     } | null;
+    /**
+     * Model turns a task run and a chat reply may take, with the code's
+     * defaults (the General settings page).
+     */
+    run_limits?: {
+        task_steps: number;
+        reply_steps: number;
+        task_default: number;
+        reply_default: number;
+        max: number;
+    } | null;
     /**
      * The release the server is running, for the General settings page.
      */