miden-client call: support advice inputs via TOML

[marijamijailovic]

The current ‎miden-client call implementation does not support advice inputs. Other client commands already accept advice map entries via TOML configuration, so we should reuse the same mechanism here for consistency.

cc @igamigo @Keinberger

[Keinberger]

+1 on reusing the TOML mechanism that exec already has.

One composition note: when remote reads (#2097) land, FPI calls against foreign accounts will often want advice data too (merkle paths, priming state). The TOML advice input path should work for both local and remote call invocations, worth keeping in mind.

[AlexWaker]

I’d like to take this one.

My rough approach would be:

• add an optional --inputs / --inputs-path argument to miden-client call, matching the existing exec behavior;
• reuse or extract the existing TOML advice-input parser from exec;
• pass the parsed entries into AdviceInputs::default().with_map(...) instead of always using empty advice inputs;
• add CLI coverage for call with advice inputs, likely mirroring the existing exec advice-input tests.

[marijamijailovic]

Hi @AlexWaker thanks for comments. This is in my pipeline to work on after FPI lands #2097.

I just do not have access to asign myself @Keinberger