Aptos Watcher Tests + event type check

[mdulin2]

The PR does the following:

• Separates the core processing functionality for the Aptos watcher into separate functions. This is to make the code more testable.
• Adds an event type verification to the message handling. This required a small change to the watcher configuration. This should be the ONLY functionality change to the watcher from the refactor.
• Rewrote the JSON modification framework in the test suite to be more modular.

[mdulin2]

I ran the reobservation flow on the production watcher for a while. It was picking up all of the events that were identifiable on Wormholesan.

[mdulin2]

This broke the tilt CI. I'll figure out why and fix that.

[djb15]

Minor comment on the code comment, but otherwise this looks good

[pleasew8t]

First pass looks good. Left a few suggestions.

[djb15]

Happy from my side. Will review any changes requested by the other reviewers

[mdulin2]

@pleasew8t I made some changes based on your feedback. Feel free to review it again.

[djb15]

Changes in the latest commit look good

[bemic]

I went over the code and my one comment would be regarding the 0x/0X, but it is already covered in Jason's comment.
The second comment, apparently Aptos addresses with stripped zeros can be used. Example from Aptos docs is 0x1. However I don't really know how rare it is.

[mdulin2]

@bemic I saw this too but didn't decide to dig further. It appears that the type and the guid get truncated. For instance, check this out: 7730cd28ee1cdc9e999336cbc430f99e7c44397c0aa77516f6f23a78559bb5

The type is returned as 0x7730cd28ee1cdc9e999336cbc430f99e7c44397c0aa77516f6f23a78559bb5::pool::ThalaSwap even though the real type would have the zeros. I'll fix the code to trim leading zeros on the comparison.