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/api/tracker/presenters/src/lib/graphql/release.resolver.ts

@@ -146,7 +146,14 @@ export class ReleaseResolver {
   archiveRelease(
     @CurrentUser() me: User,
     @Args('releaseId', { type: () => ID }) releaseId: string,
+    @Args('moveTo', {
+      type: () => ID,
+      nullable: true,
+      description:
+        'Open release of the same project that takes its unfinished tickets; none: they leave it',
+    })
+    moveTo?: string | null,
   ) {
-    return this.releases.archive(me.id, releaseId);
+    return this.releases.archive(me.id, releaseId, moveTo ?? null);
   }
 }