test(yield_resume): test MPC-style data id usage

[saketh-are]

This PR improves coverage of yield execution in two ways:

• The yield data id is written to storage when it's generated and subsequently retrieved from storage to make the resume call. This is similar to the approach being used in the MpcContract by the chain signatures use case.
• The yield and resume calls are made in two separate transactions as close together as possible.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.75%. Comparing base (db0644f) to head (7c2c1c3).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11814      +/-   ##
==========================================
- Coverage   71.76%   71.75%   -0.01%     
==========================================
  Files         796      796              
  Lines      163183   163183              
  Branches   163183   163183              
==========================================
- Hits       117110   117099      -11     
- Misses      41025    41039      +14     
+ Partials     5048     5045       -3     

Flag	Coverage Δ
backward-compatibility	0.23% <ø> (ø)
db-migration	0.23% <ø> (ø)
genesis-check	1.35% <ø> (ø)
integration-tests	37.81% <ø> (+<0.01%)	⬆️
linux	71.37% <ø> (-0.01%)	⬇️
linux-nightly	71.34% <ø> (-0.02%)	⬇️
macos	54.59% <ø> (-0.01%)	⬇️
pytests	1.62% <ø> (ø)
sanity-checks	1.42% <ø> (ø)
unittests	66.21% <ø> (-0.01%)	⬇️
upgradability	0.28% <ø> (ø)

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.