feat(server): Jira project map + trigger comment reactions

[omegent-app]

Summary

• Map Jira project keys (e.g. SA) to T3 projects via T3CODE_JIRA_PROJECT_MAP for join-or-create auto-create when an issue is unlinked.
• Map values (and T3CODE_JIRA_DEFAULT_PROJECT_ID) accept T3 project id, title, workspace basename, or absolute workspace root (/var/lib/t3/src/...) so ops can keep Discord-style paths.
• Pick order: project map → default project → sole shell project.
• Best-effort 👀 reaction on the triggering Jira comment when a delivery is accepted; remove it when the delivery finishes (like Discord/GitHub eyes). Fail-soft when the site has no public reaction API.
• Docs + unit tests for parse/resolve helpers.

Ops config example

T3CODE_JIRA_PROJECT_MAP=SA:scanner,CFG:/var/lib/t3/src/macs/configurator
# optional fallback:
# T3CODE_JIRA_DEFAULT_PROJECT_ID=/var/lib/t3/src/macs/scanner
# optional; default 1f440 (👀); empty disables:
# T3CODE_JIRA_ACK_EMOJI_ID=

Test plan

• vp test run apps/server/src/jira/JiraWebhook.test.ts
• vp check
• full monorepo typecheck
• Deploy with T3CODE_JIRA_PROJECT_MAP=SA:scanner (or full path)
• Mention bot on an unlinked SA-* issue → thread auto-creates on scanner project
• Confirm 👀 appears on trigger comment (when site supports it) and clears when done