Add You.com search as a no-auth remote MCP entry in the integration catalog

[mouse-value-add]

Desired Behavior

Agent Canvas and OpenHands agents can connect to You.com web search as a no-auth remote MCP server, selected from the shared integration catalog like the existing search providers.

Today every web-search MCP entry in the catalog (tavily, exa, firecrawl, kagi) requires an API key, so a fresh install has no working web search until the user signs up with one of those providers. You.com exposes an anonymous free tier on its MCP endpoint (https://api.you.com/mcp?profile=free) that works with zero setup — a good zero-configuration option to offer alongside the keyed ones.

Acceptance Criteria

• integrations/catalog/youcom-search.json exists: shttp transport to the keyless free-tier endpoint, auth.strategy: none
• youcom-search added to the intentionally-public remote MCP ids in tests/test_catalogs.py
• integrations/catalog-index.js regenerated with npm run build:integrations
• Opt-in live smoke test (RUN_YOUCOM_MCP_LIVE=1) exercises you-search through the same create_mcp_tools stack the Agent Canvas probe uses
• Existing integrations, search defaults, and saved settings are untouched

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label):

• The ### Actual Behavior section must describe reproducible steps
  and include a command such as uv run pytest, pytest, python,
  pip, npm run, or node.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] ...).

Enhancements (enhancement label):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• The issue has neither the bug nor enhancement label, so its readiness criteria cannot be evaluated. Add the appropriate label.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

This is an automated readiness check posted by a workflow.

[mouse-value-add]

Friendly nudge on triage: the readiness checklist above says everything is in place except the type label — this is an enhancement (new no-auth remote MCP catalog entry, no existing behavior changed), but I don't have permission to apply labels here. Could a maintainer add enhancement (and then ready-for-dev)? PR #600 is blocked on the linked-issue readiness gate and is otherwise green on its side of the checks.