✨ refactor(console_setting): migrate console settings to model_setting auto-injection

Backend
- Introduce `setting/console_setting` package that defines `ConsoleSetting` struct with JSON tags and validation rules.
- Register the new module with `config.GlobalConfig` to enable automatic injection/export of configuration values.
- Remove legacy `setting/console.go` and the manual `OptionMap` hooks; clean up `model/option.go`.
- Add `controller/console_migrate.go` providing `/api/option/migrate_console_setting` endpoint for one-off data migration.
- Update controllers (`misc`, `option`, `uptime_kuma`) and router to consume namespaced keys `console_setting.*`.

Frontend
- Refactor dashboard pages (`SettingsAPIInfo`, `SettingsAnnouncements`, `SettingsFAQ`, `SettingsUptimeKuma`) and detail page to read/write the new keys.
- Simplify `DashboardSetting.js` state to only include namespaced options.

BREAKING CHANGE: All console-related option keys are now stored under `console_setting.*`. Run the migration endpoint once after deployment to preserve existing data.

web/src/pages/Detail/index.js

@@ -1231,10 +1231,10 @@ const Detail = (props) => {
                         {faqData.map((item, index) => (
                           <Collapse.Panel
                             key={index}
-                            header={item.title}
+                            header={item.question}
                             itemKey={index.toString()}
                           >
-                            <p>{item.content}</p>
+                            <p>{item.answer}</p>
                           </Collapse.Panel>
                         ))}
                       </Collapse>