feat(aionrs): attribute AI/ML API traffic on the wire

[Lookoff-AIMLAPI]

Conversations never carried attribution.

The desktop client sets HTTP-Referer / X-Title in ClientFactory.ts, but the only caller routed through that code is the built-in image-generation MCP server. Chat and model listing go through this crate and out via aionrs, which wrote authorization and content type and nothing else — so the headers existed and reached almost no traffic.

What changed

commit
1	build(fork-only)	points the six aion-* deps at the aionrs branch carrying extra_headers
2	feat(aionrs)	resolves the attribution headers and carries them into the aionrs config
3	build(fork-only)	the lockfile commit 1 generated

Commits 1 and 3 are fork-only and drop the moment extra_headers lands upstream and aionrs cuts a tag — at which point the dependency goes back to a tag and commit 2 stands alone as the upstreamable change. They are separate and first so every commit here compiles on its own.

Upstream half: aimlapi/aionrs-aimlapi#1 — a generic extra_headers map on TransportCompat, no provider named anywhere in it.

Why the host match is exact

is_aimlapi_host mirrors is_openai_host beside it rather than doing a contains. That matters more than it looks: AI/ML API serves a request with a wrong or missing partner id normally and simply attributes it to nobody, so every failure mode here is silent. A substring match would hand our partner id to whoever registers api.aimlapi.com.example.test, and nothing at runtime would report it.

So the tests cover the near-misses, not just the hit:

• the lookalike domain, the not-api. prefix, and the host appearing in a query string — all must get no headers
• OpenAI, OpenRouter and an empty base URL — no headers
• the is_full_url early return, which exits before the rest of the compat work: a user who pasted a complete endpoint is still talking to the same host, and must still be attributed
• the partner id still matches the gateway’s ^part_[A-Za-z0-9]{1,64}$, since a malformed one fails silently and nothing else would catch it

Both places that apply compat overrides — manager::aionrs::agent and services::provider_health — carry the map through, extending rather than assigning so a preset that already has headers keeps them.

Verification

1005 tests in aionui-ai-agent pass; cargo check clean; cargo fmt clean.

Removing the single line that sets the headers, with the tests kept, fails exactly the two that assert they are sent — and leaves the three that assert they are not sent elsewhere passing, which is what those should do.