chore(deps): update dependencies with minimal risk (axios, body-parser, express, storybook, nodemailer and eslint)

[lucaslobatob]

Description

Axios

• The project already uses axios@1.12.0, however the audit report was flagging axios@0.25.0.
• Using yarn why axios, it was identified that wait-on@6.0.1 depended on the older Axios version.
• Updated wait-on to 9.0.3, which resolved the outdated Axios dependency.
• Axios was intentionally kept at 1.12.0:
  The latest version (1.13.4) contains CVE-2025-58754 (High) — a DoS vulnerability related to unvalidated data: URLs.
  Related Ticket chore: Update axios from 0.25.0 to 0.30.0 #2224

Body-parser

• Updated from 1.20.1 to 1.20.3.
• The upgrade to the latest major version (2.2.2) was postponed because body-parser is tightly coupled with Express and NestJS.
• A major upgrade should be done after updating these frameworks to avoid breaking changes.
  Related Ticket chore: Update body-parser from 1.20.1 to 1.20.3 #2225

Express

• Updated to 4.19.2.
• Migration to 5.2.1 is planned for a future iteration.
  Related Ticket chore: Update Express from 4.18.2 to 4.19.2 #2226

Storybook

• Updated to 7.6.21.
• Upgrade to the latest major version (10.2.4) will be handled separately due to breaking changes.
  Related Ticket chore: Update Storybook from 7.6.20 to 7.6.21 #2227

Nodemailer

• Updated to 7.0.11.
• Upgrade to 8.0.0 deferred for a future PR.
  Related Ticket chore: Update nodemailer from 6.10.1 to 7.0.11 #2228

ESLint

• Updated to the latest version 9.39.2.
• As a development-only dependency, this update does not affect runtime behavior and ensures access to the latest bug fixes and improvements.
• As part of this upgrade, the project was migrated from the legacy .eslintrc configuration to the new Flat Config format (eslint.config.mjs), which is required by ESLint v9.
• The Dockerfile was updated accordingly to include the new configuration file in the build context, preventing CI build failures related to missing ESLint configuration.
  Related Ticket chore: Update eslint from 7.0.0 to 9.26.0 #2229

Type of change

• Bug fix (non-breaking change which fixes an issue)

Testing

Provide relevant testing instructions. What scenarios are impacted? What build may be necessary to test this change?

Developer Checklist

General

• Code is appropriately commented, particularly in hard-to-understand areas
• Repository documentation has been updated (Readme.md) with additional steps required for a local environment setup.
• No console.log or related logging is added.
• No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).
• Documented with TSDoc all library and controller new functions

Tests

• All existing unit and end to end tests pass across all services
• Unit and end to end tests have been added to ensure backend APIs behave as expected

Test IDs

• Include the test ID when adding new tasks or components.
• Check that test IDs are present in the modified components.

Merge Request Review Checklist

• An issue is linked to this PR and these changes meet the requirements outlined in the linked issue(s)
• High risk and core workflows have been tested and verified in a local environment.
• Enhancements or opportunities to improve performance, stability, security or code readability have been noted and documented in Project do Github issues if not being addressed.
• Any dependent changes have been merged and published in downstream modules
• Changes to multiple services can be deployed in parallel and independently. If not, changes should be broken out into separate merge requests and deployed in order.