When triggering an event with "twitch event trigger", the tool will generate a single GUID that is shared in use for both the Subscription ID (.subscription.id in JSON) and the Twitch-Eventsub-Message-Id HTTP header.

While this isn't an issue in most cases, it became clear after adding in functionality for #176. In the SQLite database, it will use the ID given for both the subscription ID and the Message ID, which becomes problematic for specific use cases of reproducing issues. Basically, since they're intertwined, when you use the --subscription-id flag, it sets both, therefore never allowing a perfect reproduction of an event found in production.