Issue to be solved

The crypto contract offers crypto tools that are fully developed in the cadence language and don't have to be built-in in the language. It makes more sense to take the crypto contract outside of the Cadence repo and add it as an independent standard library core-contract.

This issue is a follow-up on the discussion in #1447 (comment)

Suggested Solution

Moving the Crypto contract out of Cadence will require:

• Moving the contract to the Flow core contracts repository (https://github.com/onflow/flow-core-contracts) (tiny)
  Move tests (small)
• Deploy the contract on all chains (medium)
• Add state migration which migrates existing stored values to the respective new deployed contract (large)

No additional work in the contract itself is required, we had already previously refactored it to be deployable like any other contract