Issue Description

Currently, when a user executes the /listening command in the Real Dev squad Discord server, their name gets updated to include Can't Talk after their name. For instance, it appears as 🎧 achintya-chatterjee-Can't Talk. However, the intended behaviour is missing, as the user is not server muted or voice channel muted in any channel of the Real Dev Squad Discord server. We need to enhance this functionality so that users are server muted or voice channel muted upon executing the /listening command.

Expected Behavior

1. When users execute the /listening command with the boolean value set to True, their server name should be updated to Can't Talk after their name, and they should be server muted or voice channel muted.

2. When users execute the /listening command with the boolean value set to False, their server name should be updated to remove Can't Talk from their name, and they should not be server muted or voice channel muted.

Current Behavior

• Executing the /listening command updates the user's name with Can't Talk but fails to server mute or voice channel mute them based on the boolean value provided.

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

1. Execute the /listening command with the boolean value set to True.
2. Observe that the user's name is updated to include Can't Talk but they are not server muted or voice channel muted.

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

• The boolean value option is currently live on production but does not effectively implement server mute or voice channel mute actions upon command execution.

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.