chore/revert samply bump

[not-matthias]

It tried to fix an issue in flamegraphs with wrong attributed callchains, but breaks recursive/deep flamegraphs.

[greptile-apps]

Confidence Score: 4/5

[High risk] Reverts a dependency to an earlier commit.

The PR does not appear safe to merge while the default profiler breaks recursive and deep flamegraphs.

Findings

1.  Recursive flamegraphs break ▶

Fix with agent prompt

### Issue 1
crates/samply-codspeed:1
This revert restores the Samply revision that, as the PR description notes, breaks recursive and deep flamegraphs. Samply is still the default wall-time profiler, so benchmarks with those call stacks will produce broken flamegraphs even though callchain attribution improves.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR reverts the pinned Samply submodule revision to address incorrectly attributed flamegraph callchains.

• Samply is the default wall-time profiler.
• The PR description identifies a resulting regression for recursive and deep flamegraphs.

_{Reviews (1) · Last reviewed commit: "Revert "chore: bump samply-codspeed""}

[codspeed]

Merging this PR will degrade performance by 13.82%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

❌ 1 (👁 1) regressed benchmark
✅ 32 untouched benchmarks
⏩ 4 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
👁	WallTime	memtrack track tar	8 s	9.3 s	-13.82%

---

_{Comparing chore/revert-samply-bump (98ef901) with main (7c135cc)}

Footnotes

1. 4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩