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/http/dto/requests.dto.ts

@@ -1148,6 +1148,19 @@ export class SetIssueSprintDto {
   sprintId!: string | null;
 }
 
+export class ArchiveReleaseDto {
+  @ApiPropertyOptional({
+    type: String,
+    nullable: true,
+    format: 'uuid',
+    description:
+      'Open release of the same project that takes its unfinished tickets; null or absent: they leave it',
+  })
+  @IsOptional()
+  @IsUUID()
+  moveTo?: string | null;
+}
+
 export class PublishReleaseDto {
   @ApiPropertyOptional({
     type: Boolean,