Diya fix(userStatus): Fixed User Lifecycle Issues

[DiyaWadhwani]

Description

Fixes the backend user lifecycle status management flow — specifically a 500 error on immediate deactivation, missing field projections, stale cache after reactivation, and restores lifecycle email handlers that were removed by a previous unidentified PR.
Fixes # (High) — User deactivation/reactivation/pause lifecycle flow

Related PRS (if any):

This backend PR is related to the frontend PR #5264.

Main changes explained:

• Update userProfileController.js — add deactivatedAt to the findById projection in changeUserStatus. This field was missing from the projection but being assigned in the DEACTIVATE case, causing Mongoose to throw a validation error on user.save() which returned an empty {} 500 response.
• Update userProfileController.js — fix the catch block in changeUserStatus to return { message, name } instead of the raw error object, which serializes to {} and makes debugging impossible.
• Update userProfileController.js — fix handleUserStatusSave to clear reactivationDate and endDate in the allusers cache when the action is ACTIVATE, so getAllUserProfile does not return stale lifecycle fields after reactivation.
• Update userProfileController.js — restore lifecycle email handlers for pause, separation, scheduled separation, reactivation, and final day cancellation that were removed by a previous PR. These handlers are called inside handleUserStatusSave and are required for notifying users and admins of status changes.

How to test:

Follow frontend PR for testing instructions.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud