Hermes Agent centralizes browser automation

This is a substantial architectural cleanup that should make Hermes easier to maintain and simpler for agents to operate, though Camofox users now manage an extra service boundary.

• –One browser_exec surface reduces tool-selection ambiguity and duplicate maintenance.
• –A native Python launcher now handles Chromium lifecycle, profile isolation, leases, and orphan cleanup.
• –Camofox remains available for anti-detection browsing without keeping its specialized backend in core. Camofox plugin docs.
• –Existing Camofox configurations and saved logins are designed to migrate automatically.
• –The tradeoff is operational complexity: Camofox still requires a separately running browser server.