fix(mcp): OAuth DCR still advertises the pre-Apache client identity

### What happened

MCP OAuth dynamic client registration still sends:

- `client_uri`: `https://github.com/maka-agent/maka-agent`
- `software_id`: always `maka-desktop`

The repository moved to Apache (`https://github.com/apache/maka`, website `https://maka.apache.org/en/`). TUI already passes `clientName: maka-tui`, but DCR still labels the software as desktop. Consent screens and IdP policy that key off `client_uri` / `software_id` therefore see a stale identity.

Expected: `client_uri` is the Apache product homepage; `software_id` matches the running client (`maka`, `maka-tui`, or `maka-desktop`).

### How to reproduce

1. Configure a remote MCP server that requires OAuth.
2. Start login so Maka performs RFC 7591 dynamic client registration.
3. Inspect the registration body (or the authorization server's client record).

### Environment

- Maka version or commit: `main` @ 194275030
- Surface: Desktop / TUI (both construct `McpOAuthProvider` via `@maka/mcp`)

### Logs, screenshots, or additional context

Hardcoded in `packages/mcp/src/oauth.ts` `clientMetadata`. Introduced by #2920; not updated after the Apache transfer. Tokens, redirect URIs, and the authorization flow itself are unaffected.