feat(bench): add tooling for synthetic native transfer benchmarks

[mooori]

Adds tooling to benchmark native token transfers with the benchmark-native-transfer command. The accounts involved in that benchmark can be generated with create-sub-accounts. Examples of how to execute both commands are given in the justfile. Documentation is available in benchmarking_synthetic_workloads.md.

The tooling is based on Rust and near-jsonrpc-client. Having the Rust toolchain installed should be sufficient to use it.

This PR is rather big. Splitting it up into smaller pieces would result in parts that don't fully support running a workload. I assume that wouldn't be favorable.

The code added here is benchmark tooling only which doesn't affect neard, so I it shouldn't be able to break anything in production.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.48%. Comparing base (4ee8111) to head (f53e7b6).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #12570      +/-   ##
==========================================
- Coverage   70.48%   70.48%   -0.01%     
==========================================
  Files         845      845              
  Lines      171985   171985              
  Branches   171985   171985              
==========================================
- Hits       121227   121221       -6     
- Misses      45644    45650       +6     
  Partials     5114     5114              

Flag	Coverage Δ
backward-compatibility	0.16% <ø> (ø)
db-migration	0.16% <ø> (ø)
genesis-check	1.29% <ø> (ø)
linux	69.41% <ø> (+0.01%)	⬆️
linux-nightly	70.05% <ø> (-0.01%)	⬇️
pytests	1.60% <ø> (ø)
sanity-checks	1.41% <ø> (ø)
unittests	70.31% <ø> (-0.01%)	⬇️
upgradability	0.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[akhi3030]

I think it is fine to merge this in and we can make improvements as needed as the benchmarking evolves or when others who are using it find ways of making improvements to it.