feat(honcho): prompt for local JWT during self-hosted setup

[haran2001]

Summary

• Adds a local JWT / bearer token prompt to the self-hosted (local) branch of hermes honcho setup. Users running Honcho with AUTH_USE_AUTH=true and an AUTH_JWT_SECRET can now paste their server-signed JWT through the wizard instead of disabling auth entirely (the previous workaround called out by the issue).
• The local token is stored under the host block (hosts.<host>.apiKey in honcho.json), not the top-level apiKey field. get_honcho_client already treats a host-block apiKey on a localhost/127.0.0.1 base URL as an explicit local-auth opt-in (_host_has_key path), so the SDK call now sends the JWT as the bearer token instead of the "local" placeholder. Cloud/hybrid switching is unaffected (top-level apiKey is left alone).
• Blank input keeps the existing local no-auth behaviour, so existing self-hosted deployments without AUTH_USE_AUTH keep working unchanged.
• Adds a Self-Hosted Honcho with Authentication subsection to the user-guide Honcho docs.

Test Plan

• python -m pytest tests/honcho_plugin/test_cli.py -q -o 'addopts='
  • Covers two new cases: local setup with a JWT writes to hosts.<host>.apiKey (and leaves the cloud apiKey untouched); blank JWT on a fresh local config leaves both apiKey slots unset.

Closes #29885

[teknium1]

This looks implemented on current main. Automated hermes-sweeper review found the same self-hosted Honcho JWT setup path already landed.

Evidence:

• plugins/memory/honcho/cli.py:579 prompts for local Honcho auth and plugins/memory/honcho/cli.py:603 asks for a Local JWT / bearer token; non-blank input is stored in the host block at hermes_host["apiKey"] on line 608.
• plugins/memory/honcho/client.py:841 uses a host-block apiKey as the explicit localhost auth opt-in and otherwise uses the local no-auth placeholder.
• tests/honcho_plugin/test_cli.py:140 covers the JWT case, and tests/honcho_plugin/test_cli.py:162 covers blank JWT preserving local no-auth behavior.
• website/docs/user-guide/features/honcho.md:109 documents the self-hosted authenticated setup flow.
• Landed in 827ce602dbed199f665f3975b61303aace2963ea (fix(honcho): harden self-hosted setup paths), which includes Closes #29885 and is contained in v2026.6.5.