Consume Discord role ID API in Real Dev Squad backend and refactor hardcoded role IDs

Issue Title: Consume Discord role ID API in Real Dev Squad backend and refactor hardcoded role IDs

Description:

To leverage the recently created Discord role ID API (refer to https://github.com/Real-Dev-Squad/discord-slash-commands/issues/79), we need to integrate it into the Real Dev Squad backend. This integration will allow us to consume the API and dynamically retrieve role IDs, eliminating the need for hardcoded role IDs in our codebase. By implementing a consumption service and refactoring the existing code, we can ensure accurate and up-to-date role ID information within our backend.

Requirements:

1. Develop a consumption service within the Real Dev Squad backend that interacts with the Discord role ID API.
2. Incorporate the consumption service into the appropriate modules and functions to replace the existing hardcoded role IDs.
3. Verify that the consumption service successfully retrieves the role IDs from the Discord role ID API and incorporates them in the backend functionality.

Additional Information:

The consumption service should be implemented with appropriate error handling and consider scenarios where the API may return errors or invalid responses. It is crucial to thoroughly test the backend functionality after the refactor to ensure its proper functioning with the newly consumed role IDs.

Acceptance Criteria:

• The consumption service should be developed and integrated into the Real Dev Squad backend.
• The existing hardcoded role IDs should be replaced with calls to the Discord role ID API through the consumption service.
• The consumption service should handle errors and provide appropriate error responses when interacting with the Discord role ID API.
• Thorough testing should be conducted to verify that the backend functionality works correctly with the dynamically retrieved role IDs.

Note:

This follow-up issue is vital for aligning the Real Dev Squad backend with the Discord role ID API. By consuming the API and eliminating hard-coded role IDs, we ensure accurate and up-to-date role information within our backend, leading to more robust and flexible functionality.

Start by locating the hardcoded Discord role IDs and the backend modules that use them, then review the Discord role ID API described in the linked issue. Done means the backend retrieves role IDs through a consumption service, handles API errors or invalid responses, removes the hardcoded values, and has tests covering the refactored functionality.