Feat: Client validate method

[cbrzn]

This PR aims to add the validate function to the client, being able to guarantee that the client can communicate with the given wrapper URI ahead-of-time

The interface is the following:

interface ValidateOptions {
  recursive: boolean
  abi: boolean
}
validate(uri: Uri | string, options: ValidateOptions) -> boolean

• If abi is true, make sure the ABI from 1st level dependencies are available (the ones from importedModuleType)
• If recursive is true, it will check all uris and make sure it can resolve them

Also, a compare function has been implemented in js/manifests/wrap to compare two array of method definitions, this function allow us to make sure that dependencies are equal and wont fail in runtime

[krisbitney]

This is amazing! I think this will be an extremely useful addition to the client. Very awesome work.

I made some suggestions for possible changes, and I highlighted a couple of minor mistakes.

A feature that could be nice (likely for a future PR) would be the ability to ignore validation of some URIs. To me, it's really convenient that it is possible to use a wrapper without all of its dependencies. A dependency might only be necessary for some methods that aren't being used. So it would be nice to have a way to incorporate that sort of information into the validation check.

I want to reiterate once again how amazing this is. The options you included here are really fantastic. 🐐🐐🐐

[krisbitney]

This is such a cool feature!

[Niraj-Kamdar]

This is awesome!

[pileks]

compare.ts is exporting a single function. Would it make sense to rename it to compareSignatures.ts, additionally export default the func?
Maybe also move it into a utils folder?

I'm thinking about this mainly from a ease-of-use, ease-of-finding point of view.