chore: update derive_more to stable version (#2961)

## What ❔

Updates `derive_more` to a stable version.

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

We're currently on beta and this is a requisite for supporting
[foundry-zksync](https://github.com/matter-labs/foundry-zksync).

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

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

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

Cargo.toml

@@ -117,7 +117,7 @@ codegen = "0.2.0"
 criterion = "0.4.0"
 ctrlc = "3.1"
 dashmap = "5.5.3"
-derive_more = "=1.0.0-beta.6"
+derive_more = "1.0.0"
 envy = "0.4"
 ethabi = "18.0.0"
 flate2 = "1.0.28"

core/lib/types/src/snapshots.rs

@@ -270,11 +270,11 @@ where
 pub struct SnapshotRecoveryStatus {
     pub l1_batch_number: L1BatchNumber,
     pub l1_batch_root_hash: H256,
-    #[debug("{} (raw: {})", utils::display_timestamp(**l1_batch_timestamp), l1_batch_timestamp)]
+    #[debug("{} (raw: {})", utils::display_timestamp(*l1_batch_timestamp), l1_batch_timestamp)]
     pub l1_batch_timestamp: u64,
     pub l2_block_number: L2BlockNumber,
     pub l2_block_hash: H256,
-    #[debug("{} (raw: {})", utils::display_timestamp(**l2_block_timestamp), l2_block_timestamp)]
+    #[debug("{} (raw: {})", utils::display_timestamp(*l2_block_timestamp), l2_block_timestamp)]
     pub l2_block_timestamp: u64,
     pub protocol_version: ProtocolVersionId,
     #[debug(