refactor: sdk

[jmdev3]

Description

Re-build squid sdk

• re implement most of the existed methods
• design good solution for handling cosmos and in the future more chains if needed with handlers
• error handling, for now I just keep it simple, let's iterate once we understand how error is going to be handle at api lvl, and maybe we can share implementation with type package
• unit test

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)
• Refactor (code improvement)
• Styles (adding, editing or fixing styles)
• Unit test

How Has This Been Tested?

Please describe the steps to test.

Evidence

Please add some evidence like screenshots or records.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• 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

[0x1NotMe]

Please remove package-lock.json

[0x1NotMe]

We should at least complete linting ?