fix: reuse host Seq instance in Development, remove local seq service

- Seq on 5341 conflicts with ItemTracker dev environment
- Dev compose now points to host.docker.internal:5341 (shared Seq)
- Removed seq service and notification_seq volume from dev compose

Ref: IT-628

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

docker/environments/docker-compose.Development.yml

@@ -3,7 +3,7 @@ services:
     environment:
       - ASPNETCORE_ENVIRONMENT=Development
       - App__ConnectionString=Host=db;Port=5432;Database=notification_service;Username=postgres;Password=postgres
-      - Serilog__WriteTo__1__Args__serverUrl=http://seq:5341
+      - Serilog__WriteTo__1__Args__serverUrl=http://host.docker.internal:5341
     ports:
       - "5200:8080"
 
@@ -11,7 +11,7 @@ services:
     environment:
       - DOTNET_ENVIRONMENT=Development
       - App__ConnectionString=Host=db;Port=5432;Database=notification_service;Username=postgres;Password=postgres
-      - Serilog__WriteTo__1__Args__serverUrl=http://seq:5341
+      - Serilog__WriteTo__1__Args__serverUrl=http://host.docker.internal:5341
 
   db:
     image: postgres:17
@@ -24,16 +24,5 @@ services:
     volumes:
       - notification_db:/var/lib/postgresql/data
 
-  seq:
-    image: datalust/seq:latest
-    environment:
-      ACCEPT_EULA: "Y"
-    ports:
-      - "5342:80"
-      - "5341:5341"
-    volumes:
-      - notification_seq:/data
-
 volumes:
-  notification_db:
-  notification_seq:
+  notification_db: