Feat/Fix: Add Prospects to Subcourse

[realmayus]

• Add prospect list in course overview to allow instructors to add prospects (frontend part of Store prospect chats in subcourse entity backend#1093)
• This reuses the waiting list component
• Update browserslist

[Jonasdoubleyou]

(would prefer one change per PR)

[JeangelLF]

(This can be tackled in a separate task) I noticed a small, unexpected behavior:

When a pupil clicks on Kursleiter:in kontaktieren, they are immediately marked as a prospect on the CoursePage, even if they haven't sent a message yet. This feels a bit unexpected (At least for me 😅)

Could we:

• Filter out empty chat prospects: Only show users as prospects once they've sent a message.
• Add a confirmation modal: Inform the user that they’ll be added as a prospect after confirming.

---

Other than that, it looks good, thank you! 💯

[JeangelLF]

We could also tackle this in a separate task:

It would be nice to include a button to open the chat with a specific prospect.

We just need to add a prop to WaitingListProspectList

onContact?: (pupilId: string) => void

and pass it to the ParticipantRow (which already renders a chat button).
Then, on the SingleCourseStudent, we just navigate to that conversation.
What do you think?

[realmayus]

Nice idea! I'll implement it here.

[realmayus]

How could we implement filtering out the empty chats?
Either, we could

• fetch the chat data from TalkJS on every call of the resolver, or
• the backend could set a flag in the prospect chat DB entity
  • for that, the backend would have to be notified when the first message was sent in a chat (possibly via a TalkJS webhook?).

I think the latter should be our preferred approach for performance reasons.
What do you think? Did I miss any more obvious solutions?

[JeangelLF]

he backend could set a flag in the prospect chat DB entity
for that, the backend would have to be notified when the first message was sent in a chat (possibly via a TalkJS webhook?).

That one makes sense. But now that I think about it twice, even if we filter out empty chats, the flow still would be a bit weird. It would be something like:

1. SuS clicks on Kursleiter kontaktieren
2. SuS sends whatever message on the chat (under the hood, this already marks the user as a prospect)
3. HuH adds the user to the course
4. SuS gets a notification that they joined the course (???)

This feels a bit off. I think we should just add a modal informing the user about what happens if they proceed to the chat.
What do you think? 👀

[realmayus]

I think this does make sense, as HuH know that prospects are interested users that contacted them via chat. We should change the notfication action though, good idea. Then we can have something like "Max has added you to course X"