test(011-agent-ticket-queue): harden afterAll against wildcard SLA policy contamination

Same class of cross-file test-isolation gap already fixed in
orchestration-flow.test.ts and sla-escalation-flow.test.ts (010's own
regression work): a wildcard (non-product-scoped) SLA policy from
another suite can match this file's own tickets too, leaving a real
sla_run row that RESTRICTs the ticket delete. Also cleaned up several
orphaned wildcard SLA policies that had accumulated in the shared
throwaway test database from earlier runs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

tests/integration/agent-ticket-queue.test.ts

@@ -166,6 +166,10 @@ describe('Agent ticket queue (User Stories 1-2)', () => {
     await prismaClient.hierarchyNode.deleteMany({ where: { name: 'ATQ Node' } });
     await prismaClient.agentSkill.deleteMany({ where: { agentId: { in: [agentXId, agentYId] } } });
     await prismaClient.ticketMessage.deleteMany({ where: ticketFilter });
+    // A wildcard (non-product-scoped) SLA policy from another concurrently-running suite (e.g.
+    // sla-escalation-flow.test.ts's own "Global policy") can match these tickets too, leaving a
+    // real sla_run row that would otherwise RESTRICT this delete.
+    await prismaClient.sLARun.deleteMany({ where: ticketFilter });
     await prismaClient.ticket.deleteMany({ where: { id: { in: createdTicketIds } } });
     await prismaClient.problem.deleteMany({ where: { productId } });
     await prismaClient.agent.deleteMany({ where: { teamId } });