feat(crypto): Update crypto deps (#4587)

## What ❔

Update crypto dependencies

Fix the issue with compilers. 
Ethereum foundation released a new compiler with 2 versions under the
same patch and it resulted an error inside svm-rs-build. The fix for the
library has been released under version 0.5.22, but it requires a new
rust. Simple upgrade to the newest nightly makes the crypto dependencies
not buildable.

I tried a few more version without a success. 

The best and easies way was hardcode the list of compilers and set the
env with.

But because we start the build from different places. It's required to
copy .cargo folder everywhere

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- The `Why` has to be clear to non-Matter Labs entities running their
own ZK Chain -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.

---------

Signed-off-by: Danil <[email protected]>

Author: Deniallugo

.cargo/config.toml

@@ -1,2 +1,4 @@
 [net]
 git-fetch-with-cli = true
+[env]
+SVM_RELEASES_LIST_JSON = { value = "etc/svm_release_list.json", relative = true }

core/.cargo/config.toml

@@ -0,0 +1,2 @@
+[env]
+SVM_RELEASES_LIST_JSON = { value = "../etc/svm_release_list.json", relative = true }

core/Cargo.lock

@@ -251,19 +251,19 @@ rust-eigenda-signers = "0.1.6"
 # However, for the historical version of protocol crates, we have lax requirements. Otherwise,
 # Bumping a crypto dependency like `boojum` would require us to republish all the historical packages.
 
-circuit_encodings = "=0.153.4"
-circuit_sequencer_api = "=0.153.4"
-circuit_definitions = "=0.153.4"
+circuit_encodings = "=0.153.5"
+circuit_sequencer_api = "=0.153.5"
+circuit_definitions = "=0.153.5"
 crypto_codegen = { package = "zksync_solidity_vk_codegen", version = "=0.32.6" }
 
-kzg = { package = "zksync_kzg", version = "=0.153.4" }
+kzg = { package = "zksync_kzg", version = "=0.153.5" }
 
 zk_evm_1_3_1 = { package = "zk_evm", version = "0.131.0-rc.2" }
 zk_evm_1_3_3 = { package = "zk_evm", version = "0.133" }
 zk_evm_1_4_0 = { package = "zk_evm", version = "0.140" }
 zk_evm_1_4_1 = { package = "zk_evm", version = "0.141" }
 zk_evm_1_5_0 = { package = "zk_evm", version = "=0.151.8" }
-zk_evm_1_5_2 = { package = "zk_evm", version = "=0.153.4" }
+zk_evm_1_5_2 = { package = "zk_evm", version = "=0.153.5" }
 
 fflonk = "=0.32.6"
 bellman = { package = "zksync_bellman", version = "=0.32.6" }