Add Paperclip backend option and gateway adapter

[iamlukethedev]

Summary

• add paperclip as a first-class Studio/runtime adapter type across settings normalization, gateway connection handling, and runtime provider creation
• add a dedicated Paperclip runtime provider and a new bundled WebSocket adapter at server/paperclip-gateway-adapter.js
• expose Paperclip in connection UIs (connect screen, floating connection panel, office settings panel) with local preset URL defaults
• document setup (README.md, docs/paperclip-gateway.md, cross-link from Hermes doc) and add npm run paperclip-adapter
• add targeted unit coverage for adapter-type normalization/defaulting and gateway profile restore behavior
• harden Paperclip adapter handshake flow by wrapping connect request handling in exception-safe logic so upstream setup failures return internal_error responses instead of dropping the socket

Scope notes

• adapter currently supports core read/chat surfaces needed for office visibility (agents.list, sessions.*, chat.*, status, models.list, config/approvals shims)
• unsupported write-heavy surfaces return explicit not_implemented responses for clear UI behavior

Testing

• targeted unit tests: tests/unit/useGatewayConnection.test.ts, tests/unit/gatewayEnvDefaults.test.ts, tests/unit/studioSettings.test.ts, tests/unit/studioUpstreamGatewaySettings.test.ts
• manual UI verification in browser: PAPERCLIP • CONNECTED remains stable after office load and 30s idle wait
• walkthrough artifacts:
  • paperclip_connection_stability_after_office_load.mp4
  • Paperclip connected initial
  • Paperclip connected after 30s

_{To show artifacts inline, enable in settings.}