fix(ai-registry): correct search query for MCP "From registry" link

[safisa]

What it does

Fixes #17739.

The MCP "From registry" link pre-filled the Extensions search with the raw registry serverId (e.g. io.github.ChromeDevTools/chrome-devtools-mcp). RegistrySearchFilter strips the reverse-DNS domain labels (io, github) from entry ids while still requiring every query term to match, so those stripped labels could never match and the linked server was filtered out — the search showed no results.

The bridge now sets the query via RegistrySearchFilter.meaningfulIdentifier(serverId), the same reduction the filter matches against, so the linked server is reliably surfaced.

How to test

1. Add an MCP server from the AI registry (e.g. chrome-devtools).
2. In AI Configuration → MCP Servers, click "From registry" next to the server.
3. The Extensions view opens and shows the server (previously the search box was filled but empty).

Or run the added unit test:

npx mocha ./packages/ai-registry/lib/browser/mcp/mcp-registry-ui-bridge-impl.spec.js

Breaking changes

• This PR introduces breaking changes and requires careful review.

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines
• User-facing text is internationalized using the nls service (no user-facing text changed)

[sgraband]

Thanks for the contribution. While this improves the topic a bit it does not work all the time, e.g. for this mcp server https://ai.open-vsx.org/?server=io.github.upstash%2Fcontext7. This together with the resulting strings not looking that nice i would be much more in favor of fixing the search to be much more stable in this regard. WDYT? Would you be interested in looking into that?

Edit: Also if the user copies the id from the website it should be findable.

[safisa]

Reworked to fix RegistrySearchFilter instead of transforming the query in the bridge:

• matches() now reduces an id-shaped query (reverse-DNS + / path) the same way it reduces entry ids, so the full id — copied from the website or set by the "From registry" link — is findable.
• meaningfulIdentifier() keeps distinctive owner labels, dropping only the TLD and hosting namespaces (e.g. github), so com.cloudflare.mcp/mcp → cloudflare mcp mcp pinpoints it instead of mcp mcp matching everything.
• The bridge now just searches the raw serverId.

Verified against the live registry: all 27 MCP servers and all 102 skills are found by their raw id, the exact entry is pinpointed, and git still doesn't match every io.github.*. Tests added.

[sgraband]

Thank you thats a nice change! Could you please squash your commits?