Spotted a major error in the CSV import component.

#configmakeathon update!!!

I initially designed and integrated this component to also scan the incoming CSV file and match for already exisitng emails on the guest list to avoid duplicate guest info on the list. This was properly implemented and a good implementation at that.

But a problem surfaced; the system began to reject some imports by rejecting the emails that aren't assigned to a Crowd 9 account... which isn't necessary and needed because a planner may have eventually put that email manualy or may have edited a previously exported CSV file from the system.

I fixed this and the system works perfectly fine now.

Now when you import a CSV, guests will be added directly to the event without needing to match their emails to existing Crowd9 accounts. The system supports a mix of both:

Registered users who sign up through the app (have user_id and user_profile)

Imported guests who are added via CSV (have guest_name and guest_email, no user_id)

To even better avoid duplicate prevention; the sytem now uses a new key pattern event_guest_email:{eventId}:{email} to prevent duplicate imports based on email+event combination.