[Feature]: Support connecting QwenPaw Pet to a remote daemon

## Summary

I want QwenPaw Pet (the desktop companion app) to support connecting to a remote QwenPaw daemon. This will allow users to run the daemon/agents persistently on a server while displaying the Pet interface on their daily personal computer to monitor states and interact with the remote agent.

## Component(s) Affected

- [ ] Core / Backend (app, agents, config, providers, utils, local_models)
- [ ] Console (frontend web UI)
- [ ] Channels (DingTalk, Feishu, QQ, Discord, iMessage, etc.)
- [x] Skills
- [ ] CLI
- [ ] Documentation (website)
- [ ] Tests
- [ ] CI/CD
- [ ] Scripts / Deploy

## Problem / Motivation

In many real-world scenarios, users prefer to run the QwenPawdaemon persistently on a dedicated remote server (e.g., a home server, a cloud VPS, or a lab workstation) so that the agents can run 24/7 and handle background tasks continuously.

However, the "Pet" application is a desktop companion designed for daily interaction and status visualization. Naturally, users want this Pet to sit on their active personal computer/laptop screen.

Currently, because Pet forces a local daemon, users cannot use the Pet app to interact with or monitor their remote QwenPaw instances. If they want to see their agent's status, they are forced to run everything locally, which breaks the "run-in-the-background-on-a-server" workflow.

## Proposed Solution

I propose adding a "Connection Settings" option in the Pet desktop application:

1. Toggle Switch: Allow users to switch between Local Daemon (default) and Remote Daemon.
2. If "Remote Daemon" is selected:
- The Pet app should bypass starting its internal Python environment and local daemon.
- Provide configuration inputs for:
- Daemon Host/URL (e.g., http://192.168.1.100:port or ws://...)
- Authentication Token (Crucial for security when exposing the daemon over the network).
3. Daemon-side Enhancements: Ensure the QwenPaw daemon can bind to LAN/WAN IPs (e.g., 0.0.0.0 instead of just 127.0.0.1) and supports basic API Key/Token verification to secure remote connections.

## Alternatives Considered

None.

## Additional Context

None.

## Willing to Contribute

- [ ] I am willing to open a PR for this feature (after discussion).