Complete Cadence 1.0 and Atree inlining migration

[j1010001]

Issue to be solved

Problem: We are planning to run atree register inlining migration, as well as all migrations needed for Cadence 1.0 in a single network upgrade (crescendo release). This issue describes all tasks which we need to complete to have a complete migration for both features, including validation of all migrated Cadence values.


Critical Tasks:

• [x] #2989
• [x] #2990
• [x] #3177
• [x] #3178
• [x] https://github.com/onflow/flow-go/pull/5204
• [x] https://github.com/onflow/flow-go/pull/5488
• [x] https://github.com/onflow/flow-go/pull/5605
• [x] https://github.com/onflow/flow-go/pull/5622
• [x] #3179
• [x] #3048
• [ ] (never merge) https://github.com/onflow/flow-go/pull/5349
• [ ] https://github.com/onflow/flow-go/pull/5554
• [ ] https://github.com/onflow/flow-go/pull/5636
• [ ] #3229

Nice to have / optional / requested:

• [x] https://github.com/onflow/atree/pull/359
• [ ] Performance optimization - Change the atree register inlining migration output to “intermediate” format - registers sorted by account, which will be an input into the Cadence 1.0 migrations (this is saving time as we’d need to sort the registers again to leverage the concurrent account-based migration extracted from the Atree register inlining migration PR here: https://github.com/onflow/flow-go/pull/5128)
• [x] #3170
• [x] https://github.com/onflow/flow-go/pull/5386
• [x] https://github.com/onflow/flow-go/pull/5389
• [x] https://github.com/onflow/flow-go/pull/5499
• [x] https://github.com/onflow/flow-go/pull/5609

Suggested Solution

No response

[turbolent]

@j1010001 @fxamacker I think this is done now, right? OK to close?