feat: forc call json output

[zees-dev]

Description

This PR adds JSON output support for forc-call CLI.

Additionally, it adds JSON support for tracing-subscriber in forc-tracing - with option to omit logs from other libraries (via regex).

• JSON tracing-subscriber ignores colored output
• Forc-call hooks into this tracing-subscriber (using Json variant) to output JSON response

Changelog

This pull request introduces enhancements to the forc-call plugin, focusing on improving output formatting, streamlining verbosity handling, and updating test cases to reflect these changes.
The most significant updates include the addition of a JSON output format, the removal of the Verbosity struct, and modifications to test cases to handle optional results.

Output Formatting Enhancements:

• Added a new Json variant to the OutputFormat enum for outputting full tracing information in JSON format. Implemented the Write trait for OutputFormat to handle different output styles. (forc-plugins/forc-client/src/cmd/call.rs, forc-plugins/forc-client/src/cmd/call.rsR60-R87)
• Updated the Command struct to include a short option (-o) for specifying the output format. (forc-plugins/forc-client/src/cmd/call.rs, forc-plugins/forc-client/src/cmd/call.rsL319-R319)

Verbosity Handling Simplification:

• Removed the Verbosity struct and its associated methods. Verbosity is now directly represented as an integer (cmd.verbosity) for simplicity. (forc-plugins/forc-client/src/cmd/call.rs, [1]; forc-plugins/forc-client/src/op/call/call_function.rs, [2] [3] [4] [5]

Test Case Updates:

• Modified test cases to handle optional results by calling .unwrap() on the result field where applicable. This ensures compatibility with changes to how results are processed. (forc-plugins/forc-client/src/op/call/call_function.rs, [1] through [2]

These changes improve the usability and maintainability of the forc-call plugin, making it more robust and user-friendly.

Note: This is a pre-requisite to resolve #7019; the output script in the JSON can be directly parsed into a tx.json file for forc-debug.

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[codspeed-hq]

CodSpeed Performance Report

Merging #7156 will not alter performance

_{Comparing feat/forc-call-json-output (bcd7c55) with master (bd38136)}

Summary

✅ 22 untouched benchmarks