Fix spelling error: 'upcomming' -> 'upcoming' across the codebase

[Dotify71]

Description:
While exploring the codebase, I noticed that the word "upcoming" is misspelled as "upcomming" (with a double 'm') across several filenames, class names, and variables.

For consistency and code readability, we should fix this typo throughout the project.

Files affected include (but are not limited to):

• lib/controllers/upcomming_rooms_controller.dart
• lib/models/appwrite_upcomming_room.dart
• lib/views/widgets/upcomming_room_tile.dart

Classes/Variables affected:

• UpCommingListTile -> UpcomingListTile
• AppwriteUpcommingRoom -> AppwriteUpcomingRoom
• upcommingRoomsController -> upcomingRoomsController

Steps to Reproduce / Proposed Changes:

1. Rename the affected files to use upcoming_ instead of upcomming_.
2. Do a global find and replace for upcomming -> upcoming and UpComming -> Upcoming.
3. Verify that all imports are updated correctly so the app still compiles.

I'd be happy to open a PR for this if it's assigned to me!

[github-actions]

👋 Hello @Dotify71!
Thank you for opening this issue. Our team will review it soon. 🚀

• If you can, please provide more details like steps to reproduce, expected vs. actual behavior, and screenshots (if applicable). 📌

We appreciate your contribution! 💡

[Dotify71]

Hi! Since this is a codebase refactoring/typo fix, UI screenshots and behavioral steps don't quite apply here. I've detailed the affected files and proposed renaming steps in the issue description above. I would love to tackle this if it can be assigned to me! Thank you.

[sunny-bits123]

Hi, I would like to work on this issue and fix the spelling mistake. I will submit a PR soon.

[Dotify71]

Hi @sunny-bits123, thank you for your interest! However, as the author of this issue, I am already actively working on fixing this and will be opening a PR shortly whenever i get a green signal from maintainers.

[Mayank4352]

Hey @Dotify71, We're in the middle of refactoring the complete codebase and the issue raised by you is already fixed in #824. Thank you for pointing this out.

[Dotify71]

Got it, @Mayank4352! Thanks for the heads up. Glad to hear the refactoring covers this. I'll go ahead and close this issue. Best of luck with the rest of the refactoring!

[github-actions]

🔒 Issue Closed - Thank You, @Dotify71!
This issue has been resolved or is no longer relevant.

• If you have further questions, feel free to open a new issue. 💡

Thanks for helping improve the project! 🚀