[lesnik512]

This puts the data from #51 and #52 on the page. Feedback asked for two things: a warning when a picked tag ships issues that also depend on unreleased work elsewhere, and a clear answer to why a task shows up for a tag or a row.

Changes:

• Left behind by these picks. A list above the Release tabs. For every Jira task the picks ship, and for every issue related to one, it lists each service where that issue has changes no pick covers: SHOP-38 → web: needs 1.9.0, SHOP-38 is blocked by SHOP-44 → admin: not merged, SHOP-38 → mobile: not in this report. A related issue with no changes at all that isn't done in Jira gets its status instead: SHOP-36 is blocked by SHOP-45: To Do. Changes already in production and closed merge requests aren't listed. Unlike the existing plan line, this works for hand picks and for issues that ship anyway, not only for ticked issues.
• Rows show named, linked or both next to each Jira key, from via.
• Jira tasks name the merge requests or commits that bring each task: from api !57, web !120.
• Issues list. Related issues (via_relation) get their own group at the end. Hovering a key shows its relations.
• Every relation type is listed with Jira's own label, so a blocks link shows up too. If that gets noisy, filtering by direction is a small follow-up.
• tagRow replaces the inline findIndex in untickMissed, because the new code needs the same lookup.
• The demo gets SHOP-44 (blocks SHOP-38, open MR in admin) and SHOP-45 (blocks SHOP-36, To Do, no changes). The Issues list there now has 8 issues.
• docs/page.md describes all of it. Russian strings are added.

Tests: four new browser tests cover the left-behind list before and after a second pick, the row labels, task sources, and the related group with the hover text. They failed before the change. just lint-ci, just test-ci and just test-smoke pass.