tests(nano): test actions order

[glevco]

Motivation

Improve nano tests by making sure sending actions in different orders doesn't impact the final result.

Acceptance Criteria

• Update test_actions.py to run tests with different action orders in tests with more than one action.

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged

[github-actions]

Bencher Report

Branch	tests/nano/actions-order
Testbed	ubuntu-22.04

Click to view all benchmark results

Benchmark	Latency	Benchmark Result minutes (m) (Result Δ%)	Lower Boundary minutes (m) (Limit %)	Upper Boundary minutes (m) (Limit %)
sync-v2 (up to 20000 blocks)	📈 view plot 🚷 view threshold	1.85 m (+11.07%) Baseline: 1.67 m	1.50 m (81.03%)	2.00 m (92.56%)

🐰 View full continuous benchmarking report in Bencher

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.65%. Comparing base (c10ec87) to head (aa75eb8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1354      +/-   ##
==========================================
+ Coverage   85.63%   85.65%   +0.01%     
==========================================
  Files         429      429              
  Lines       32450    32450              
  Branches     5068     5068              
==========================================
+ Hits        27790    27794       +4     
+ Misses       3631     3630       -1     
+ Partials     1029     1026       -3     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.