Add staged contract migration

[SupunS]

Closes onflow/cadence#3038

[codecov-commenter]

Codecov Report

Attention: 24 lines in your changes are missing coverage. Please review.

Comparison is base (8af35c0) 58.45% compared to head (838a812) 55.64%.

Files	Patch %	Lines
...il/ledger/migrations/staged_contracts_migration.go	87.80%	11 Missing and 4 partials ⚠️
...execution-state-extract/execution_state_extract.go	0.00%	9 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                     @@
##           feature/stable-cadence    #5300      +/-   ##
==========================================================
- Coverage                   58.45%   55.64%   -2.81%     
==========================================================
  Files                         911      998      +87     
  Lines                       86472    96256    +9784     
==========================================================
+ Hits                        50547    53563    +3016     
- Misses                      32208    38673    +6465     
- Partials                     3717     4020     +303     

Flag	Coverage Δ
unittests	55.64% <81.81%> (-2.81%)	⬇️

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.

[turbolent]

Great work!

[SupunS]

Not sure if this is the proper way to do this: We need to run contract migration for all accounts first, before running other migrations for any account.

[turbolent]

TestCadenceValuesMigration is failing, not quite sure why

[turbolent]

Sorry, that was my bad, I had changed the format of the error message!

[SupunS]

ah no, that's totally fine! It's a bit fragile/not really a good practice to assert on the error messages anyway. But don't really have a better alternative in this case really. In that test I want to make sure the 'correct' error is on the correct account, path, and the key (which is pretty much the entire error message)