feat(screening_monitoring): add configuration part

[OrriMandarin]

This pull request introduces a new feature for managing screening monitoring configurations in the backend. It adds the necessary API endpoints, data models, database migration, repository logic, usecase layer, and security enforcement for creating, reading, updating, and listing screening monitoring configs. The changes are grouped below by theme.

API and Routing

• Added new HTTP endpoints for listing, creating, retrieving, and updating screening monitoring configs in routes.go and implemented their handlers in handle_screening_monitoring.go. [1] [2]

Data Modeling and DTOs

• Introduced ScreeningMonitoringConfig model and related create/update types in models/screening_monitoring_config.go.
• Added corresponding DTOs and adaptation/validation logic in dto/screening_monitoring_config.go.

Database Layer

• Added a migration to create the screening_monitoring_configs table, including fields and constraints, and an index for organization ID.
• Implemented repository methods for CRUD operations on screening monitoring configs in screening_monitoring_repository.go and related DB model adaptation in db_screening_monitoring_config.go. [1] [2]

Usecase and Security Enforcement

• Added a usecase layer for screening monitoring configs, including security checks for read/write operations. [1] [2]
• Implemented security enforcement for screening monitoring config permissions, including new permission types. [1] [2] [3] [4]

Integration

• Registered the new usecase and security enforcement in the usecases factory.

These changes together enable full lifecycle management of screening monitoring configuration entities, including secure access control and persistence.

[linear]

MAR-1325 Create monitoring screening configuration

[Copilot]

Pull Request Overview

This PR introduces a comprehensive screening monitoring configuration management feature for the backend system. The implementation adds secure CRUD operations for managing screening monitoring configurations at the organization level.

Key Changes:

• Added new REST API endpoints for managing screening monitoring configurations (list, create, retrieve, update)
• Implemented complete data persistence layer with database migration, repository methods, and model adapters
• Integrated permission-based security enforcement for read/write operations on screening monitoring configurations

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
api/routes.go	Registered four new HTTP endpoints for screening monitoring config operations
api/handle_screening_monitoring.go	Implemented HTTP handlers for all screening monitoring config endpoints
dto/screening_monitoring_config.go	Defined DTOs with validation and model adaptation for API layer
models/screening_monitoring_config.go	Created domain models for screening monitoring config and CRUD operations
models/permission.go	Added two new permission types for screening monitoring read/write access
repositories/migrations/20251023145610_screening_monitoring_config.sql	Created database table with constraints and indexes
repositories/dbmodels/db_screening_monitoring_config.go	Implemented database model and adapter for screening monitoring config
repositories/screening_monitoring_repository.go	Implemented repository methods for database CRUD operations
usecases/screening_monitoring/usecase.go	Created usecase layer structure with repository interface
usecases/screening_monitoring/config.go	Implemented business logic for all screening monitoring config operations
usecases/security/enforce_security_screening_monitoring.go	Implemented permission enforcement for screening monitoring operations
usecases/usecases_with_creds.go	Registered new usecase and security enforcement in factory

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The Enabled field is defined in the model with a TODO comment but is not included in the database migration, repository operations, or DTOs. This creates an inconsistency where the field exists in the domain model but cannot be persisted or accessed. Either implement full support for this field across all layers, or remove it from the model until it's ready to be implemented.

Suggested change

Enabled bool

[Copilot]

The DBScreeningMonitoringConfig struct is missing the Enabled field that exists in the database migration (line 14 of the SQL file). This inconsistency will cause the field to be ignored when reading from or writing to the database. Add the Enabled bool \db:"enabled"`` field to match the database schema.