Move event presence from initiative facilitator to initiative coordinator

Maybe we actually want both roles helping with this, assuming they have sufficient time? It's definitely an initiative coordinator area, but it's also not a single-person task unless that person abandons all their other work in favor of doing this during the weeks before the event.

Gábor and I generally worked on this collaboratively. The original idea was to offload my usual task of spending a week chasing down 50-80 maintainers' schedules, getting them to provide their availability, checking with Dries for his availability, and then solving the intricate puzzle of scheduling 8 different critical discussions around all those requirements to the committer team facilitator, since scheduling and sorting this kind of data is a facilitation skill, not an initiative or release management one. (I literally had a shell script to collate availability and suggest meeting times since it was such a complicated puzzle to solve. We tried to have Dries' EA help with this also but she didn't use the shell script and so there were attendance conflicts etc. that were not addressed.

More recently (and especially since my layoff from DAT) I just haven't helped as much as I used to, and we only ended up having a handful of meetings at post-COVID events anyway.

I think the words "- Plan strategic core "birds of a feather" sessions at major Drupal events." don't refer to the "hard problem meetings" we used to have but rather to support the funnel of contributors of initiatives. Point 2 in https://www.hojtsy.hu/blog/2022-apr-13/gather-interest-and-involve-contr... basically. This would fall squarely within the initiative coordinator, at least on the meta level like the rest of the things. So I don't understand the need to move this to a followup, its IMHO misleading to put this under the core team facilitator since the core team did not have open BoFs at events that I know of? So its very oddly placed there IMHO.

If this point is about the "hard problem meetings" then IMHO it does not sound like that, so it needs to be reworded in the original issue and also does not need a followup.

@Gábor Hojtsy We started using the BOF system to schedule the meetings many years ago due to concerns (mostly from @webchick) about them being "closed" or "secret", and to make it easier to work with the DA to schedule them without a special funding source. Others (possibly also @webchick) had concerns about our slang "Hard Problems" being... dunno, discouraging or implying a burden to participants or something. So that's at least my assumption regarding the language here.

And that was already in fact in my initial proposal from 2018, so I think we just need the wording change.

Or well, no MR yet.

How about the slightly more specific:

Plan "birds of a feather" meetings for major Drupal events on strategic core topics that require committer input.

Or something.

And again, I think ideally we would want to recruit additional committer team facilitators (somehow... possibly with funding) to assist with the process, because it's not scalable for it to rely only on @Gábor Hojtsy.

Re #5. I moved this to another issue because it was specific to one role. Perhaps, a better option would have been to split them in one issue per role but I was thinking that the role descriptions were already decided and this was not a complete review.

Whether it is needed or not there is a MR available here.