[Bug] - Fetched events can have incorrect transaction IDs if the events are emitted in different AccountUpdates

[MartinMinkov]

Description

fetchEvents uses the Archive Node API to fetch events/actions from the Archive Node. When fetchEvents were implemented, the internal type of Events was updated to reflect network information such as block and transaction information.

Due to a bug in the Archive Node API, events have incorrect transaction information. Actions are not affected in this case since actions do not have transaction information fetched from the API. Only events do.

Currently, in SnarkyJS, the return value of fetchEvents is incorrect since transaction information should be defined for each event. To fix, we need to change the GraphQL query for fetchEvents and change the internal types used in SnarkyJS to add transaction information to events instead.