fix: memory leak in event triggers

[niekschoemaker]

Please describe the changes this PR makes:
The trigger creates a "trigger" function which saves the context into the _listeners map in the client.

Each time this function get's triggered the response is pushed into the responses array, which is created once, on startup. This causes a memory leak which saves all responses during the lifetime of the bot.

By moving the respones array into the function itself this is resolved and it will only return the responses for that specific trigger and the array can be garbage collected after this.

For a quick example of this bug on production (running for around a week with 100k members):

This array uses about 250 MB of memory, which is about 90% of all memory usage, and the array only contains empty objects returned from the execute function.

[vijayymmeena]

@niekschoemaker thanks, could you please bump the patch as well for auto release.

Just run npx changeset and npx chageset version

[niekschoemaker]

@niekschoemaker thanks, could you please bump the patch as well for auto release.

Just run npx changeset and npx chageset version

Done, did it with a force push to avoid a unecessary commit.