feat: add support for numbers in multicall

[kfastov]

Closes #2245

Introduced changes

• Added new enum type Input with variants String and Number(i64) to support both string and numeric inputs in TOML files
• Updated DeployCall and InvokeCall structs to use Vec<Input> instead of Vec<String> for their inputs field
• Modified parse_inputs function to handle both string and numeric input variants
• Added #[serde(untagged)] attribute to enable seamless deserialization of both input types from TOML

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

Other notes

• Numbers larger than 2^64 are not supported by TOML format: https://toml.io/en/v1.0.0#integer
• However, numbers outside i64 range cannot be supported currently due to an issue in the toml parser

[Arcticae]

@kfastov can you please also test the case where the number exceeds the limit (so we make sure it fails with a reasonable message)?

[Arcticae]

@kfastov bump

[Arcticae]

@kfastov are you still working on this? Please let me know so i can reassign if you're not :)

[kfastov]

Hi @Arcticae
Sorry for delayed reply, I had a multi-day transfer with no internet, I am ready to finish this PR now, and I'll do it today or tomorrow :)

[Arcticae]

Thx for the update 👍

[Arcticae]

cc @cptartur can you assign someone to take a second look?

[franciszekjob]

Left only two nits, looking good 👍

[kfastov]

@franciszekjob Addressed the nits, please check

[franciszekjob]

LGTM

[Arcticae]

@kfastov thx for your contribution!