chore: fix call response type & Signature type

[tabaktoni]

Motivation and Resolution

Fix TS issue with contract.call response
Signature #565

Usage related changes

Type-defined but more flexible Signature:
If used as string[] it can be any implementation and default implementation use WeierstrassSignatureType

Development-related changes

No interface changes just redefined types

export type WeierstrassSignatureType = weierstrass.SignatureType;
export type ArraySignatureType = string[];
export type AnySignatureType = string | number | ArraySignatureType | WeierstrassSignatureType;
export type Signature = ArraySignatureType | WeierstrassSignatureType;

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes
• Updated the docs (www)
• Updated the tests
• All tests are passing

[netlify]

✅ Deploy Preview for starknetjs canceled.

Name	Link
🔨 Latest commit	44e3792
🔍 Latest deploy log	https://app.netlify.com/sites/starknetjs/deploys/642ab82229be620008d9954f

[github-actions]

🎉 This PR is included in version 5.4.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀