[EPIC] Enable testing of contract update to Cadence 1.0 in Emulator

[j1010001]

Issue to be solved

Why: Developers need to test their ability to upgrade their existing contract to Cadence 1.0 version. When we release Emulator running Cadence 1.0, this would not be possible because if the upload of a contract that does not parse/typecheck with Cadence 1.0 will fail.

This step is required to collect data for the next stage, described in #2865.

Tasks for Emulator 1.0 RC1 release (enables dapp testing):

Beta Give feedback

1. Enable devs to deploy old (0.4x-based) Cadence contracts to emulator and then upgrade to C1.0. This will likely require emulator-only contracts.add method which skips type checking and enables any code to be uploaded, and parser that can parse contracts based on both v04 and 1.0 versions to perform the update restrictions. This requires the update checker to be able to parse both v0.42 and 1.0 contract versions.
2. Optimize storage migration: Allow skipping of values #3157
   Improvement +1
   
3. Improve static type and entitlements migrations: Update array/dictionary type directly #3158
   Improvement +1
   
4. [Cadence 1.0] Perform atree storage health check after migrating account flow-go#5486
   +0
5. [Cadence 1.0] Improve Migration flow-go#5479
   +0
6. Emulator command for migrating contracts/state to Cadence 1.0 flow-cli#1433
   Cadence 1.0 Feature Feedback +3
   
7. Release this emulator build to community - this enables devs to test their contract upgrade to C1.0.

Suggested Solution

No response

[j1010001]

Required for: onflow/flow-emulator#468

[j1010001]

Can be closed after the new Emulator build is released.

[turbolent]

Is the requirement for closing this issue that the updated update checker has been completed, or is that a separate issue/milestone?

I assume that work is part of #2865, in which case this issue can be considered in-review/done.

[j1010001]

Is the requirement for closing this issue that the updated update checker has been completed, or is that a separate issue/milestone?

I assume that work is part of #2865, in which case this issue can be considered in-review/done.

No, let's close this when the first version of this is out and create a new issue if the upgrade checker needs adjustments.

[SupunS]

I guess we can close this issue now?

[turbolent]

Yeah, I think we can close this now, given there's no known work left to be done. 🎉 👏

We can maybe leave #3098 open until it's been confirmed that the latest CLI preview release works as expected.