Enhance fines management with points history and PDF receipt features

[vthish]

This pull request introduces several significant changes to the fines and licensing system, focusing on improved handling of fines, license status automation, and enhanced data relationships. The main themes are: stricter device login handling, improved fine issuance and payment logic, enhanced data modeling for officers and scans, and more robust automation around license activation and suspension.

Key changes include:

Fines and License Status Logic Improvements

• Fine issuance now uses a scanToken (JWT) to securely associate fines with licenses, and introduces automatic handling of overdue fines and license activation/suspension based on point thresholds and court cases. Points now accumulate upwards, triggering suspensions and revocations at 24, 50, and 100 points respectively. [1] [2]
• Fine payment logic is updated to prevent payments for already paid or overdue/court-case fines, and to only reactivate licenses when appropriate. Bulk payments follow similar rules and provide clear user feedback. [1] [2]
• Added automation to reactivate suspended licenses when all fines are cleared or suspension periods expire. [1] [2] [3]

Data Model and Schema Enhancements

• The Prisma schema adds new relationships: QR_Scan_History now references Traffic_Officer, and Temporary_License records the issuing officer. Traffic_Officer is related to both QR scans and temporary licenses. [1] [2] [3]
• The Fine_Status enum introduces a new COURT_CASE status, and Driving_License points now start at 0 instead of 24, with a new suspended_Until field to track suspension periods. [1] [2]

Security and Authentication

• Device login now returns a specific error structure when a device mismatch is detected, requiring OTP verification for new devices instead of a generic unauthorized error.
• The AuthRequest interface and password change logic are simplified to use id instead of sub for user identification. [1] [2] [3]

API and Service Additions

• New endpoints for traffic officers to retrieve their stats and fines.
• The FinesService now injects JwtService for scan token verification and is registered in the module. [1] [2]

General Robustness

• Error handling is standardized: NotFound and BadRequest exceptions are thrown without detailed messages for invalid operations (e.g., missing entities, invalid actions). [1] [2] [3] [4] [5]

These changes collectively make the fines and licensing system more secure, maintainable, and aligned with real-world business rules.

---

References:

• Fines and License Status Logic: [1] [2] [3] [4] [5]
• Data Model and Schema: [1] [2] [3] [4] [5]
• Security and Authentication: [1] [2] [3] [4]
• API and Service: [1] [2] [3]
• Robustness: [1] [2] [3] [4] [5]

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.