feat: move unfinished tickets between releases

- Bulk editing gets «Release…» (open releases or none), and the list
  view a release filter, also reachable from each release («Ver en la
  lista», ?release=).
- Archiving a release asks where its unfinished tickets go, as closing
  a sprint does: ReleaseArchivedEvent carries `moveTo` (an open release
  of the same project, or none) and the saga moves them there; finished
  ones stay. In GraphQL, REST and the MCP's archive_release.
- Chapter 10 lists the next features and the ideas to weigh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

libs/web/tracker/infrastructure/src/lib/adapters/graphql-issues.gateway.ts

@@ -255,6 +255,8 @@ export class GraphqlIssuesGateway extends IssuesGateway {
           assigneeId: change.assigneeId ?? null,
           noSprint: change.sprintId === null ? true : null,
           sprintId: change.sprintId ?? null,
+          noRelease: change.releaseId === null ? true : null,
+          releaseId: change.releaseId ?? null,
           priority: (change.priority ?? null) as never,
           addLabels: change.addLabels ?? null,
         },