api: resolve patchset summary by slug as fallback

[zraza-xlnx]

The GET /api/patchset summary handler only looked up patchsets by numeric id or message-id. Forge ingested patchsets are addressed by slug (for example reponame-79), so the web UI's summary requests for those patchsets fell through to the message-id lookup, matched nothing, and returned 404.

UI links reviews by slug, but the API never resolved slugs. This PR adds that fallback so slug links stop 404 error.

sashiko/static/index.html

Line 1967 in 39f6ce9

const target = `#/patchset/${encodeURIComponent(p.slug || p.message_id || p.id)}`;

Chain the non numeric lookups by result: try message-id first, then fall back to slug when the message-id lookup finds nothing. This mirrors the branching already used by the patchset details handler.

Regression test results

Test area	Example	Parent	PR
Repository-name and legacy slug lookup	id=linux-next-725 (reponame-prnum)	FAIL: HTTP 404	PASS: HTTP 200
Numeric/message-ID lookup	id=42 selects numeric patchset 42	PASS	PASS

This change is backward compatible.

[zraza-xlnx]

Reviewed by @pieterj-xilinx and @alexaust-xlnx internally.

[sashiko-bot]

Sashiko review — v2

Commit 1/1 — ec4a4db3 api: resolve patchset summary by slug as fallback

• [HIGH] In src/api.rs (get_patchset_summary), the sequential database
  fallback omits the fast string heuristic used elsewhere. As a result,
  looking up a valid slug forces an unindexed full table scan on
  message_id, which can cause severe latency and SQLite stalls on a
  growing database. Furthermore, valid message ID lookups defer their log
  until after the query completes, and missing message IDs incorrectly fall
  back to log and search as a slug.

Full review and stage logs on sashiko.sashiko.dev