MUL-6228: resolve full-UUID issue refs locally instead of a resolver GET (#7167)

* perf(cli): resolve full-UUID issue refs locally instead of a resolver GET

A full UUID is self-identifying, yet resolveIssueRef sent it through
GET /api/issues/<uuid> just to learn the id it already had — and agents
fire several multica issue calls back-to-back during run bootstrap, so
the round-trip was paid several times per run (GH #7017).

Full-UUID refs now short-circuit to a lowercased resolvedID with zero
HTTP requests, pinned by test the same way the short-prefix rejection
is. Identifier refs (MUL-123) keep the fetch — that mapping genuinely
needs the server. Two accepted consequences, per the issue: messages
built from Display show the UUID rather than the issue key for
full-UUID invocations, and a nonexistent UUID now 404s on the command's
own request instead of the resolver's — every write path re-validates
server-side (e.g. parent_issue_id on create checks GetIssueInWorkspace),
so nothing is stored on the strength of the ref alone.

* fix(cli): preserve issue keys in reorder messages

Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: damon.zhou <damon.zhou@huolala.cn>
Co-authored-by: Sol-Boy <sol-boy@multica-ai.local>
Co-authored-by: multica-agent <github@multica.ai>