chore: Update nestjs/common from 9.2.0 to 10.4.22

[lucaslobatob]

Description

Updates the @nestjs/common dependency from version 9.2.0 to 10.4.22, aligning the project with NestJS and ensuring compatibility with other ecosystem dependencies. The update brings performance improvements, bug fixes and internal framework adjustments, in addition to preparing the basis for future updates to related packages. There were no changes to the application's functional behavior, just necessary adjustments to keep the project updated and stable.

Related Ticket #2256

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

• 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).

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.

[caneppelevitor]

@lucaslobatob rebase it and then we can merge