feat: teams within a project

Projects keep teams of members in their settings (settings.teams; people
outside the project are dropped, teams are archived, not removed; absent
when saving means unchanged). Tickets go to a team (`team`, also filtered
in the list and in MCP search_issues), and a comment mentioning
@[Frontend](team-FRONT) tells each of its members. Settings has the teams
with their members, the ticket a «Equipo» select, the list a team filter,
and «@» offers the teams after the people.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

libs/api/tracker/presenters/src/lib/http/dto/responses.dto.ts

@@ -79,6 +79,13 @@ export class AreaOptionDto {
   @ApiProperty() archived!: boolean;
 }
 
+export class TeamDto {
+  @ApiProperty({ example: 'FRONTEND' }) id!: string;
+  @ApiProperty({ example: 'Frontend' }) name!: string;
+  @ApiProperty({ type: [String] }) memberIds!: string[];
+  @ApiProperty() archived!: boolean;
+}
+
 export class CustomFieldDefinitionDto {
   @ApiProperty({ example: 'BROWSER' }) id!: string;
   @ApiProperty({ example: 'Navegador' }) name!: string;
@@ -108,6 +115,7 @@ export class ProjectSettingsDto {
       'Definition of done: tickets reach DONE only with their checklist ticked',
   })
   checklistBeforeDone!: boolean;
+  @ApiProperty({ type: [TeamDto] }) teams!: TeamDto[];
 }
 
 export class ProjectDto {
@@ -422,6 +430,8 @@ export class IssueDto {
   type!: string;
   @ApiProperty({ type: String, nullable: true, example: 'FRONTEND' })
   area!: string | null;
+  @ApiProperty({ type: String, nullable: true, description: 'A team id' })
+  team!: string | null;
   @ApiProperty() title!: string;
   @ApiProperty({ type: String, nullable: true }) description!: string | null;
   @ApiProperty({ example: 'IN_PROGRESS', description: 'A status id' })