add types e2e test for evm

[open-junius]

Description

The PR add e2e test cases for EVM in subtensor. All are implemented in type script.

Related Issue(s)

• Closes #[issue number]

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Other (please describe):

Breaking Change

If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Please include any relevant screenshots or GIFs that demonstrate the changes made.

Additional Notes

Please provide any additional information or context that may be helpful for reviewers.

[ales-otf]

Finally we can have it in the main repo! And having it type-safe is an additional benefit. I noticed a few code quality issues though. Additionally to them there are a lot of commented code. But feel free to ignore my comments.

[ales-otf]

thanks Junius! i've noticed just a few more issues in readme. but they are minor, you can ignore them if you wish.

[ales-otf]

missed this last time and confused now. as far as i understand it, this command does the same as cargo update in rust - it updates dependencies versions in the manifest. i suppose we wouldn't like it to be happened every time the repo is cloned. otherwise why this command is listed here particularly for this dependency?

[open-junius]

I just found out if we generate a new metadata in .papi which including the new extrinsic, for instance. But the IDE doesn't show the new one. I need run it to refresh. It is little confused. I will remove it and put it in personal notes.

[ales-otf]

oh, if it's needed to generate metadata, then it's better to keep it, but mentioned it in here.