feat: Add more buckets to call tracer (matter-labs#1137)

## What ❔

<!-- 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 ❔

<!-- 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. -->

- [ ] 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 `zk fmt` and `zk lint`.
- [ ] Spellcheck has been run via `zk spellcheck`.
- [ ] Linkcheck has been run via `zk linkcheck`.

core/lib/multivm/src/tracers/call_tracer/metrics.rs

@@ -4,10 +4,10 @@ use vise::{Buckets, Histogram, Metrics};
 #[metrics(prefix = "vm_call_tracer")]
 pub struct CallMetrics {
     /// Maximum call stack depth during the execution of the transaction.
-    #[metrics(buckets = Buckets::exponential(1.0..=1024.0, 2.0))]
+    #[metrics(buckets = Buckets::exponential(1.0..=4096.0, 2.0))]
     pub call_stack_depth: Histogram<usize>,
     /// Maximum number of near calls during the execution of the transaction.
-    #[metrics(buckets = Buckets::exponential(1.0..=1024.0, 2.0))]
+    #[metrics(buckets = Buckets::exponential(1.0..=4096.0, 2.0))]
     pub max_near_calls: Histogram<usize>,
 }