[IMP] add match details in event template to support updating match events

[Bart274]

Should help #112

[Olen]

What happens if the event is not a match? Will something break when submitting an event with match data?
I think there needs to be some checks for that.

[Olen]

@Bart274 friendly ping — pulling together a 1.2.1 release sweep and would like to include this if we can resolve the open question. Quoting the original concern from late 2024:

What happens if the event is not a match? Will something break when submitting an event with match data?

The added matchEvent: False default plus the nested matchInfo (all None) is what worries me — for a non-match event (e.g. training), do those fields get rejected by the API, silently ignored, or accepted as-is? A quick update_event against a real training event with the new template would settle it.

Happy to merge once we have that confirmation (or a small conditional that only includes matchInfo when matchEvent=True).