fix(integrations): escape catalog metadata in discovery output

[marcelsafin]

Description

Integration catalog values are untrusted JSON data, but integration search
and integration info interpolated them directly into Rich output. Bracketed
values were interpreted as markup and silently lost their literal formatting.

This routes catalog-derived IDs, names, versions, descriptions, authors,
licenses, tags, repository URLs, and source names through the module's existing
_rich_escape helper while preserving trusted status styling and lookup logic.
Unknown query IDs use the same escaped representation in not-found output.

Regression tests assign distinct Rich tags to every rendered field and verify
that each value survives literally in both commands.

Testing

• Tested locally with uv run specify --help
• Ran existing tests with uv sync && uv run pytest
• Tested with a sample project (if applicable)

Full suite: 5424 passed, 172 skipped.

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (describe below)

GitHub Copilot (GPT-5.6 Sol) autonomously identified, implemented, tested, and
self-reviewed this change on behalf of @marcelsafin.

[Copilot]

Pull request overview

Escapes untrusted integration catalog metadata before Rich rendering in discovery commands.

Changes:

• Escapes metadata displayed by integration search and integration info.
• Preserves raw IDs for registry and installed-integration lookups.
• Adds regression coverage for markup-like catalog values.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/specify_cli/integrations/_query_commands.py	Escapes catalog-derived Rich output.
tests/integrations/test_cli.py	Tests literal rendering of markup-like metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/specify_cli/integrations/_query_commands.py:381

• safe_integration_id is only used when the catalog lookup succeeds. The not-found branch still interpolates the raw integration_id at line 461, so specify integration info '[red]missing[/red]' continues to interpret the queried ID as Rich markup instead of displaying it literally. Reuse the escaped value in that branch and cover the missing-ID case as well.

    safe_integration_id = _rich_escape(str(integration_id))

[marcelsafin]

Posted for @marcelsafin by GitHub Copilot (model: GPT-5.6 Sol). Follow-up to the suppressed low-confidence review note: 86874e4 now escapes unknown query IDs in the not-found branch using the existing safe_integration_id, with a red/green regression test. Full suite: 5424 passed, 172 skipped.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[Copilot]

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Medium

[mnriem]

Thank you!