feat: add types to parse streams webhook data

[ErnoW]

---

name: 'Pull request'
about: A new pull request

New Pull Request

Checklist

• I am not disclosing a vulnerability.
• My code is conform the code style
• I have made corresponding changes to the documentation
• I have updated Typescript definitions when needed

Issue Description

Related issue: #FILL_THIS_OUT

Solution Description

[changeset-bot]

⚠️ No Changeset found

Latest commit: 223a545

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Test coverage

Title	Lines	Statements	Branches	Functions
api-utils		60.45% (295/488)	44.62% (54/121)	64.48% (69/107)
auth		100% (143/143)	90.9% (20/22)	100% (42/42)
core		90.23% (573/635)	75.3% (122/162)	84.09% (111/132)
evm-api		81.46% (466/572)	16.56% (54/326)	64.3% (191/297)
common-evm-utils		63.05% (669/1061)	35.01% (104/297)	30.43% (112/368)
sol-api		100% (20/20)	66.66% (4/6)	100% (6/6)
common-streams-utils		95.6% (674/705)	97.93% (190/194)	100% (244/244)
streams		82.72% (388/469)	64% (64/100)	73.6% (92/125)

[b4rtaz]

I wonder, maybe we should move streams types (EvmStream, EvmStreamResult etc) to a new package: @moralisweb3/common-streams. Why common? Because if I need to transfer some value from the back-end side to the front-end side we should create these types as a "common" side.

[ErnoW]

I wonder, maybe we should move streams types (EvmStream, EvmStreamResult etc) to a new package: @moralisweb3/common-streams. Why common? Because if I need to transfer some value from the back-end side to the front-end side we should create these types as a "common" side.

Interesting point. Do you think there will be any use-cases to use these types directly in the client? I think that this feature is mostly backend-only, and that the frontend will used partial data from this, mainly via specific endpoints/database lookups.

If there is no use-case then I'd prefer to keep it simple and contained in the streams package.

The base branch was changed.