Update angular packages

[marcorosa]

Bump angular packages and fix conflicts

[github-actions]

The update reflects version changes in Angular dependencies within the frontend/package.json file, moving from various versions to newer minor patch levels. This often brings bug fixes, performance improvements, and possibly minor API changes without breaking backward compatibility. Additionally, similar updates were made to some devDependencies.

Walkthrough

• Refactor: Updated Angular framework dependencies for smoother performance and reliability improvements, ensuring the frontend remains compatible and secure with the latest features and fixes.
• Chore: Raised the devDependencies versions to align with the stable versions of Angular packages, supporting the latest tooling and development enhancements.

These changes are crucial for maintaining system stability and taking advantage of the latest optimizations offered by Angular.

_{Model: gpt-4o-2024-08-06 | Prompt Tokens: 738 | Completion Tokens: 141}

[github-actions]

Here's a collaborative code review enhanced with AI assistance. These observations offer insights and suggestions to consider, though they're recommendations rather than absolute requirements. You have full ownership of your code decisions—AI simply provides additional perspective to support your development process. Use whatever guidance feels valuable and aligns with your project goals.

---

Always critique what AI says. Do not let AI replace YOUR I.
_{Model: claude-sonnet-4-20250514 | Prompt Tokens: 1557 | Completion Tokens: 530}

[github-actions]

Consider using exact versions instead of caret ranges for Angular dependencies in production applications. This ensures consistent builds across different environments and prevents unexpected breaking changes from patch updates.

"@angular/animations": "20.3.15",
"@angular/cdk": "20.2.14",
"@angular/common": "20.3.15",
"@angular/compiler": "20.3.15",
"@angular/core": "20.3.15"

This practice helps maintain build reproducibility and reduces the risk of subtle bugs introduced by automatic dependency updates.

[github-actions]

Consider updating the TypeScript ESLint parser version to match the eslint-plugin version (8.46.4) for consistency and to avoid potential compatibility issues.

"@typescript-eslint/parser": "^8.46.4"

Keeping ESLint-related packages at the same version helps prevent parsing conflicts and ensures all TypeScript linting features work correctly together.