Update to Cadence v1.2.1, Move Cadence Crypto contract on-chain

[turbolent]

Work towards onflow/cadence#3135

• Update to Cadence v1.2.1 and Go SDK v1.2.2
• Add the Crypto system contract, and e.g. deploy it to the system account during bootstrapping
• Translate import Crypto to the chain-specific contract

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 80.48780% with 16 lines in your changes missing coverage. Please review.

Project coverage is 41.14%. Comparing base (ce74abc) to head (27f56e0).
Report is 9 commits behind head on master.

Files with missing lines	Patch %	Lines
...md/util/ledger/util/migration_runtime_interface.go	0.00%	7 Missing ⚠️
fvm/environment/contract_reader.go	88.88%	2 Missing and 1 partial ⚠️
fvm/evm/stdlib/checking.go	85.71%	2 Missing ⚠️
fvm/systemcontracts/system_contracts.go	50.00%	2 Missing ⚠️
utils/unittest/execution_state.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6571      +/-   ##
==========================================
+ Coverage   41.12%   41.14%   +0.01%     
==========================================
  Files        2031     2031              
  Lines      179589   179571      -18     
==========================================
+ Hits        73862    73878      +16     
+ Misses      99521    99483      -38     
- Partials     6206     6210       +4     

Flag	Coverage Δ
unittests	41.14% <80.48%> (+0.01%)	⬆️

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]

Looks like this also needs an Emulator PR

[turbolent]

No idea why the integrations test fail, with odd errors like

could not get latest sealed block header: client: failed to construct flow.BlockHeader entity from protobuf value: protobuf message is empty

@onflow/flow-access @onflow/flow-core-protocol could you PTAL?

[turbolent]

CI failures are probably due to the SDK update, which includes a few PRs which might cause this, e.g. onflow/flow-go-sdk#778. @illia-malachyn could you PTAL?

[illia-malachyn]

sure. i'm looking into this

[illia-malachyn]

Hi @turbolent,

I've updated the SDK to align with the new protobuf message format, which now expects additional fields in the block header message. However, it seems these new fields are not being sent. I suspect that the code responsible for constructing block headers and sending them to peers hasn’t been updated to include the new fields.

I initially assumed that if the protobuf message was updated, the code responsible for sending the messages would also be updated accordingly.

The new fields that might be causing the issue are:

• LastViewTimeoutCertificate (a TimeoutCertificate)
• HighestQC (a QuorumCertificate within TimeoutCertificate)

Update 1:
TimeoutCertificate can be null. I didn't know about his. I'll fix this but we will have to move to v1.2.3 or sth to make this PR work

Update 2:
I opened a PR for this onflow/flow-go-sdk#790

[turbolent]

@illia-malachyn Thank you for looking into this and fixing it, much appreciated! Unfortunately, I don't know anything about it. @onflow/flow-core-protocol @onflow/flow-collection-and-consensus can someone familiar with timeout certificates please review onflow/flow-go-sdk#790?