fix: Use raw message_id instead of ctx.message.id in wait_for_component

[silasary]

Pull Request Type

• Feature addition
• Bugfix
• Documentation update
• Code refactor
• Tests improvement
• CI/CD pipeline enhancement
• Other: [Replace with a description]

Description

I've noticed that sometimes the Message will be None, throwing an error. This usually happens when using wait_for_component on Ephemeral messages with a long or non-existent timeout.

This switches the ID check to directly reference the message_id, rather than going through a cache lookup that may fail.

Changes

• Changed a dot to an underscore.

Related Issues

Test Scenarios

Python Compatibility

• I've ensured my code works on Python 3.10.x
• I've ensured my code works on Python 3.11.x

Checklist

• I've run the pre-commit code linter over all edited files
• I've tested my changes on supported Python versions
• I've added tests for my code, if applicable
• I've updated / added documentation, where applicable