Reorganize Events and EventSequence code

[Selene-Amanita]

Objective

Make code relating to event more readable.

Currently the impl block of Events is split in two, and the big part of its implementations are put at the end of the file, far from the definition of the struct.

Solution

• Move and merge the impl blocks of Events next to its definition.
• Move the EventSequence definition and implementations before the Events, because they're pretty trivial and help understand how Events work, rather than being buried bellow Events.

I separated those two steps in two commits to not be too confusing. I didn't modify any code of documentation. I want to do a second PR with such modifications after this one is merged.

[JoJoJet]

I agree with merging the impl blocks and placing them next to the struct -- however I'd prefer for EventSequence to be defined under Events. In general, I think it's nice for a source file to read like a table of contents. When reading, first you see how something is used, then later on you see how it's defined. I find that this style makes it easier to understand the "why" of code since you see the context for a type before its implementation details.

[JoJoJet]

Thanks for taking my advice! This file is much easier to read without the impl block split for no reason.

Marking as ready for final review, since this is a trivial change.

[Selene-Amanita]

Thank you for reviewing ^^

Part of the reason I split the two changes in two commits is so I can easily revert the second one as I knew it wouldn't necessarily win unanimous support. I'm aware the convention is to see how something is used first then how it's implemented, but I thought for this case since it's so small and doesn't really have a use in itself, and the thing that use it is pretty big, it could make sense to put it before, but yeah I think it doesn't matter and you're right.

[github-actions]

Example alien_cake_addict failed to run, please try running it locally and check the result.