Fix OOO Nickname Update - Select Active RDS Discord Users

Issue Description

• All the users who have a status in the users status model are selected irrespective of whether they are part of the Discord server or not
  With this fix, we only want to select those users who have an updated users status and who are part of the RDS Discord server. Namely using the

Expected Behavior

• Any update in the OOO for a user must be reflected successfully in their RDS Discord server nickname

Current Behavior

• In staging, post testing we are getting an error if there's a failure to fetch discord ID of a person who is unavailable

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

1. Create a Discord personal server and connect using the Discord API keys via code
2. Execute cron-jobs repository and website-backend simultaneously to test the cron job

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

[Include any additional context, logs, or details that might be helpful in addressing the issue.]

Checklist

• I have read and followed the project's code of conduct.
• I have searched for similar issues before creating this one.
• I have provided all the necessary information to understand and reproduce the issue.
• I am willing to contribute to the resolution of this issue.

Thank you for contributing to our project! We appreciate your help in improving it.

Start by tracing the cron-jobs and website-backend execution paths that use the Discord API to select users and update nicknames. Verify the users status and RDS Discord membership conditions, then reproduce the staging failure; done means unavailable users are excluded and eligible users' OOO nicknames update successfully.