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/application/src/lib/events/project.events.ts

@@ -26,7 +26,10 @@ export const projectPageEvents = eventGroup({
     memberRemoveRequested: type<{ projectId: string; userId: string }>(),
     releaseCreateRequested: type<CreateReleaseInput>(),
     releasePublishRequested: type<{ releaseId: string; force: boolean }>(),
-    releaseArchiveRequested: type<{ releaseId: string }>(),
+    releaseArchiveRequested: type<{
+      releaseId: string;
+      moveTo: string | null;
+    }>(),
     releaseNotesWriteRequested: type<{
       releaseId: string;
       notes: string | null;