Enable state migration on emulator

[SupunS]

Issue to be solved

Add a mechanism for developers to run the state migration on the emulator state. Then could combine it with the contract update on emulator (#2947) to test the end to end flow. Objective is to allow developers to:

• Use an old state with a Cadence 1.0 emulator
• Update your contracts to cadence 1.0
• Run the migration using some tool (<- this is what this issue is proposing)
• Start using the emulator with cadence 1.0 contracts + data

Suggested Solution

Draft PR: onflow/flow-emulator#557

[SupunS]

Draft PR: onflow/flow-emulator#557

Need to:

• Finalize where/how to integrate this: https://discord.com/channels/613813861610684416/1123314820763111465/1202314935053594715
• Fix import handler errors in the migration (probably need to fix this in the migration framework): Gracefully handle runtime panics in migration #3066
• Migrate core contracts

[turbolent]

Nice! Re: onflow/flow-emulator@supun: storage/migration/cadence_values_migration.go looks familiar, is this from flow-go? Can we maybe re-use the code from there?

[SupunS]

Yeah, it is similar, but needed some modifications, so copied it over there to make it easier to do the modifications at the time. Cleaned it up: onflow/flow-emulator#557

[SupunS]

I've also added the migration for system contracts. However, the value migration still fails because it fails to find the Burner contract: https://discord.com/channels/613813861610684416/1202379720776495134/1202766352956391475

[SupunS]

Came across this while testing: #3068. Not sure if this is an issue or the expected behaviour. Probably need further investigation/discussion