parse values with units in FunctionCallDefinition

[Parizval]

Motivation

Issue: #387

Refactoring data type of Value of FunctionCallDefinition and FunctionCallDefinitionStrict to U256.

PR Checklist

• Added Tests
• Added Documentation
• Ran cargo +nightly clippy --workspace --lib --examples --tests --benches --all-features --locked --fix
• Ran cargo fmt --all
• Note breaking changes in PR description, if applicable
• update changelogs
  • Update CHANGELOG.md in each affected crate
  • add a high-level description in the root changelog

[zeroXbrock]

Thanks for the PR, good first pass. I made a mistake in the original spec that requires some changes: FunctionCallDefinition.value actually does need to be Option<String> because the templater relies on strings to support placeholder injection. It's a tiny change on your end, but my mistake -- sorry bout that!

Once the changes I requested are addressed, the code will be ready to support values with units!

[Parizval]

@zeroXbrock, Could you provide your feedback on the changes ?

[zeroXbrock]

@zeroXbrock, Could you provide your feedback on the changes ?

yep, reviewing today! 🫡

[zeroXbrock]

thanks @Parizval! I realized that I made yet another mistake -- FunctionCallDefinitionStrict is supposed to hold String values -- its only guarantee is that it has a definite from field (where FunctionCallDefinition does not), but otherwise the strings it holds are to be evaluated by the Templater. Sorry for the confusion! Anyhow, I just went ahead and fixed it up. Everything works great -- thanks again for contributing!