feat: parse files when the argument values are very big

[AlexD10S]

This PR is part of the pop call parachain feature.
It improves handling the parameters with type TypeDef::Sequence similar to the approach used in PolkadotJS.

1. Properly parsing user-provided values automatically encoding the value into a hexadecimal format. (Based on this comment feat: guide user to call a parachain #316 (comment))
2. Allowing users to provide large values through a file, similar to the approach used in PolkadotJS, instead of requiring direct string input:

For testing
Run pop call parachain, input a relay chain url and select the Register a parachain ID with genesis state and code option.

◇  What would you like to do?
│  Register a parachain ID with genesis state and code 
│
◇  Enter the value for the parameter: id
│  2000
│
◇  The value for `genesis_head` might be too large to enter. Provide a file instead?
│  Yes 
│
◇  Enter the file path for the parameter `genesis_head`:
│  ../pop-node/para-2000-genesis-state
│
◇  The value for `validation_code` might be too large to enter. Provide a file instead?
│  Yes 
│
◇  Enter the file path for the parameter `validation_code`:
│  ../pop-node/para-2000.wasm

[sc-1507]

[codecov]

Codecov Report

Attention: Patch coverage is 82.75862% with 30 lines in your changes missing coverage. Please review.

Project coverage is 75.97%. Comparing base (98aaae9) to head (896ec4a).
Report is 4 commits behind head on feat-call-ui-extrinsics-limited.

Files with missing lines	Patch %	Lines
crates/pop-cli/src/commands/call/parachain.rs	81.81%	3 Missing and 15 partials ⚠️
crates/pop-parachains/src/call/mod.rs	56.00%	0 Missing and 11 partials ⚠️
crates/pop-parachains/src/call/metadata/mod.rs	97.05%	0 Missing and 1 partial ⚠️

@@                         Coverage Diff                         @@
##           feat-call-ui-extrinsics-limited     #363      +/-   ##
===================================================================
+ Coverage                            75.89%   75.97%   +0.08%     
===================================================================
  Files                                   62       62              
  Lines                                12450    12597     +147     
  Branches                             12450    12597     +147     
===================================================================
+ Hits                                  9449     9571     +122     
- Misses                                1759     1761       +2     
- Partials                              1242     1265      +23     

Files with missing lines	Coverage Δ
crates/pop-parachains/src/call/metadata/params.rs	93.30% <100.00%> (+0.51%)	⬆️
crates/pop-parachains/src/call/metadata/mod.rs	94.23% <97.05%> (+0.68%)	⬆️
crates/pop-parachains/src/call/mod.rs	76.92% <56.00%> (-5.84%)	⬇️
crates/pop-cli/src/commands/call/parachain.rs	79.23% <81.81%> (+0.56%)	⬆️

... and 1 file with indirect coverage changes

[al3mart]

Let's maybe ask directly for a file instead of asking if the user wants to paste in the terminal. I think both of these, the code and the state, will be always better managed via files.

[AlexD10S]

My approach was similar to PolkadotJS, using a simple input example like the remark extrinsic where you probably won't need a File. However, your suggestion likely makes more sense, as it helps avoid potential input issues for users.

[evilrobot-01]

I think I prefer the approach of accepting a string, which is either resolved to a file or is otherwise treated as direct input, to avoid all the additional prompts. If the extrinsic has a few fields to provide data for, it might quickly get annoying to be prompted for each one, as shown in the PR description.

i.e. "The value for {} might be too large to enter. You may enter the path to a file instead."

[AlexD10S]

Based on both opinions and to minimize unnecessary prompts, I removed the confirmation step. Now, the user input can be either a file path or a value, and pop-cli will handle the value:

cli
        .input(format!(
            "The value for `{}` might be too large to enter. You may enter the path to a file instead.",
            param_name
        ))
        .placeholder(&format!(
            "Enter a value of type {} or provide a file path (e.g., /path/to/your/file.json)",
            param_type
        ))
        .interact()?;

Refactored in this commit: f39900e

[evilrobot-01]

Looks good, some suggestions for relatively easy improvements.

[evilrobot-01]

I think I prefer the approach of accepting a string, which is either resolved to a file or is otherwise treated as direct input, to avoid all the additional prompts. If the extrinsic has a few fields to provide data for, it might quickly get annoying to be prompted for each one, as shown in the PR description.

i.e. "The value for {} might be too large to enter. You may enter the path to a file instead."

[evilrobot-01]

Consider deriving Default for the Param struct to simplify all the initializations below - Param { name: "my_name", ..Default.default() }. The benefit is that you only define those fields you care about (see type_to_param), defering the rest to default values. If the suggestion is useful, consider a PR to the base PR to introduce.

[AlexD10S]

Introduced in f2a0f76. because it solves the comment to improve tests: #363 (comment)

But I am going to prepare another PR to refactor all the rest of usages.

[AlexD10S]

The last commit 423eb3b updates a library to address a vulnerability detected by the CI during the cargo-deny check run: https://github.com/r0gue-io/pop-cli/actions/runs/12236673594/job/34130654485?pr=363
Also had to include Unicode-3.0 license in the list of allowed libraries(deny.toml) as it is compatible with pop-cli GPL-3.0 license

[evilrobot-01]

Looks good.

Note that I havent tested manually, which I wanted to do on the mean feat PR instead.