cleanup: event length naming inconsistencies

[Green-Sky]

Also applies to types.

This change is 

[codecov]

Codecov Report

Attention: Patch coverage is 85.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 72.99%. Comparing base (2457125) to head (0199c0f).

Files	Patch %	Lines
toxcore/events/group_private_message.c	66.66%	2 Missing ⚠️
toxcore/events/group_message.c	83.33%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2732   +/-   ##
=======================================
  Coverage   72.99%   72.99%           
=======================================
  Files         149      149           
  Lines       30516    30516           
=======================================
  Hits        22276    22276           
  Misses       8240     8240           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JFreegman]

Reviewed 10 of 10 files at r1, all commit messages.
Reviewable status: complete! 1 change requests, 1 of 1 approvals obtained (waiting on @Green-Sky)

---

other/event_tooling/generate_event_c.cpp line 783 at r1 (raw file):

they are :)

kinda makes no sense if you didn't see the original comment

---

toxcore/events/group_message.c line 257 at r1 (raw file):

void tox_events_handle_group_message(
    Tox *tox, uint32_t group_number, uint32_t peer_id, Tox_Message_Type type, const uint8_t *message, size_t message_length, uint32_t message_id,

message_type?

---

toxcore/events/group_private_message.c line 257 at r1 (raw file):

void tox_events_handle_group_private_message(
    Tox *tox, uint32_t group_number, uint32_t peer_id, Tox_Message_Type type, const uint8_t *message, size_t message_length, uint32_t message_id,

message_type?

[JFreegman]

Reviewed 5 of 5 files at r2, 2 of 2 files at r3, all commit messages.
Reviewable status: 1 change requests, 0 of 1 approvals obtained (waiting on @Green-Sky and @nurupo)