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/domain/src/lib/ports/gateways.ts

@@ -289,7 +289,11 @@ export abstract class ReleasesGateway {
     releaseId: string,
     force: boolean,
   ): Observable<CommandResult>;
-  abstract archive(releaseId: string): Observable<CommandResult>;
+  /** Its unfinished tickets go to `moveTo` (an open release) or leave it. */
+  abstract archive(
+    releaseId: string,
+    moveTo?: string | null,
+  ): Observable<CommandResult>;
   abstract burnup(releaseId: string): Observable<ReleaseBurnup>;
   /** A Markdown draft from the release's finished tickets (not saved). */
   abstract notesDraft(releaseId: string): Observable<string>;