Fix auto assign member to existing organization based on email domain

[skwowet]

Changes proposed ✍️

What

🤖 Generated by Copilot at 7927475

Implemented the auto-assignment feature for members and organizations. Added a new method findByDomain to the organizationRepository and organizationService classes to query organizations by email domain. Refactored the memberService class to use the new method and assign members to organizations accordingly.
​

🤖 Generated by Copilot at 7927475

Sing, O Muse, of the skillful code that was written
By the wise developers, who sought to enhance the app
With a feature that would link the members and the orgs
By the domains of their emails, as swift as Hermes' winged sandals.

Why

How

🤖 Generated by Copilot at 7927475

• Add a feature that allows members to be automatically assigned to organizations based on their email domains (link, link, link)
• Create a new static method findByDomain in organizationRepository.ts that queries the database for an organization with a matching website attribute (link)
• Rename and use the findByDomain method in memberService.ts to find and assign the organization ID to the member data (link)
• Add a new instance method findByDomain in organizationService.ts that delegates the query to the repository layer (link)
• Refactor the declaration and initialization of the organizations array in memberService.ts to improve readability and structure (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.