search_issues result link loses project filter when given a slug #1340

Calling search_issues with a project slug correctly scopes the API request to the resolved project ID, but the View these results in Sentry link puts the original slug in the project query parameter. Opening that link loses the requested project selection.

Reproduction

Use a synthetic project web-app with ID 123 and at least one matching issue:

search_issues(
  organizationSlug="example-org",
  projectSlugOrId="web-app",
  query="is:unresolved"
)

• The Sentry API request contains project=123.
• The returned search link contains ?project=web-app&query=is%3Aunresolved.
• The frontend parses the scalar project parameter as an integer; web-app becomes an empty project selection instead of selecting project 123.

Expected: the link contains project=123, matching the project used by the API request.

Cause and scope

The handler resolves the slug to an ID, but passes the original input to the formatter. The formatter forwards that value to the URL builder, which writes it unchanged into project. The frontend parser requires a numeric value.

Use the already-resolved project ID for the search link while preserving the display label and remaining URL parameters. Cover slug input, numeric input, and no project filter. This is independent of API/web hostname routing.