docs(config): fix invalid 'hermes config get' references in 3 guides

[CryptoJones]

Closes #30195.

hermes config get <key> is referenced in three guides but is not a valid subcommand — the closest existing form is hermes config show, which dumps the entire resolved config and accepts no positional arguments. Following the docs verbatim produces unrecognized arguments errors.

Going with the docs-only fix (Option 1 in the issue). The issue body suggested hermes config show | grep '^<key>', but that doesn't work for nested keys in YAML output (e.g. skills.config lives under a skills: parent), so I went with plain hermes config show plus a short "look at X in the output" hint where it reads naturally.

Changed:

• website/docs/guides/work-with-skills.md:165 — hermes config get skills.config → hermes config show (comment now points the reader at skills.config in the output)
• website/docs/guides/migrate-from-openclaw.md:228 — hermes config get session_reset → "the session_reset section of hermes config show"
• website/docs/user-guide/configuring-models.md:195 — hermes config get model → "see model.provider / model.model in hermes config show"

Verified no remaining hermes config get references in website/docs/ (the one remaining config get hit in mcp-mcporter.md is for the unrelated mcporter binary).

Option 2 in the issue (adding a real hermes config show <key> per-key getter) is the better UX but is a CLI change — happy to leave that for a follow-up if maintainers want it.

[teknium1]

Superseded by #30390, which was merged to main as part of the Bucket-1 docs-correctness sweep (PR #34781). Your PR fixed the same issue — the 'hermes config get' → 'hermes config show' fix — and the merged version preserves per-commit authorship for the contributor whose variant was the most complete. Both contributors are credited. Thanks for catching this!