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-collaboration.gateways.ts

@@ -104,9 +104,12 @@ export class GraphqlReleasesGateway extends ReleasesGateway {
       .pipe(map((d) => toCommandResult(d.publishRelease)));
   }
 
-  archive(releaseId: string): Observable<CommandResult> {
+  archive(
+    releaseId: string,
+    moveTo: string | null = null,
+  ): Observable<CommandResult> {
     return this.gql
-      .mutate(ArchiveReleaseDocument, { releaseId })
+      .mutate(ArchiveReleaseDocument, { releaseId, moveTo })
       .pipe(map((d) => toCommandResult(d.archiveRelease)));
   }