style: run cargo fmt

[PastaPastaPasta]

Issue being fixed or feature implemented

Run cargo fmt; it was failing on v3.1-dev and it was annoying me / pastaclaw

What was done?

run cargo fmt

How Has This Been Tested?

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

Summary by CodeRabbit

• Tests
  • Internal code formatting improvements with no user-facing changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

The bloom.rs test file has been reformatted to convert multi-line CoreBloomFilter initializations into single-line declarations in two test blocks. No functional or logical changes are introduced.

Changes

Cohort / File(s)	Summary
Test Formatting packages/rs-dapi/src/services/streaming_service/bloom.rs	CoreBloomFilter initialization statements consolidated from multi-line to single-line format in test blocks; whitespace and line-breaking style adjusted without altering functionality.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A formatting spree through bloom so fine,
Multi-lines dance, now condensed to one,
Tests still pass with grace and shine,
Cleaner code when parsing's done,
Brevity blooms where space was mine! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'style: run cargo fmt' accurately describes the main change in the pull request—applying code formatting via cargo fmt to fix formatting issues.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/cargo-fmt

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[PastaPastaPasta]

Trivial style only change; CI happy merging