chore(deps): update rust crate similar to v3.1.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
similar	dependencies	patch	3.1.1 → 3.1.2

---

Release Notes

mitsuhiko/similar (similar)

v3.1.2

Compare Source

• Fixed Algorithm::Lcs deadline fallback emitting edits twice, which produced
  out-of-bounds DiffOp ranges and panics when consuming timed-out diffs. #​97
• Fixed Algorithm::Lcs reporting identical subranges with zero-based indices
  instead of preserving the supplied range offsets. #​98
• Fixed Algorithm::Lcs and Algorithm::Hunt emitting zero-length delete
  operations when both inputs are empty. #​99

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codspeed-hq]

Merging this PR will degrade performance by 18.33%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 346 untouched benchmarks
⏩ 46 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	df_with_path	571 µs	699.1 µs	-18.33%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing renovate/similar-3.x-lockfile (4c98048) with main (0b214cc)²}

Footnotes

1. 46 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. ↩

2. No successful run was found on main (e7906a0) during the generation of this report, so 0b214cc was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/cut/bounded-memory (passes in this run but fails in the 'main' branch)
Skipping an intermittent issue tests/pr/bounded-memory (passes in this run but fails in the 'main' branch)
Congrats! The gnu test tests/rm/many-dir-entries-vs-OOM is now passing!