feat: createBid batching

[vertex451]

Should be merged after #392

Testing

Batcher

While provider was stopped I created 10 deployments and started a provider. During the order catchup it created expected batch of bids:

• flush batch=1 remaining=0 ← first bid fires immediately (idle)
• enqueue inFlight=true pending=9 ← rest coalesce while in-flight
• flush batch=5 remaining=4 ← first batch of 5 drains
• batch succeeded count=5
• flush batch=4 remaining=0 ← remaining 4 sent together
• batch succeeded count=4

Smart retry

I've changed a code and force first message in a batch to fail.

• flush batch=1 → injecting test failure idx=0 → ERR message failed, retrying remainder remaining=0 (msg removed, nothing left to retry → done)

• flush batch=2
  → WRN injecting test failure idx=0 → ERR remaining=2
  → WRN injecting test failure idx=0 → ERR remaining=1
  → WRN injecting test failure idx=0 → ERR remaining=0
  (all 3 stripped one by one, each caller gets individual error)

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 24f0f5b5-1e3f-475d-897f-e1afa8b6ca45

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch artem/batching-create-bid

---

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

[vertex451]

There's no runner.Result involved anymore - the channel type reflects the new reply mechanism directly.

[vertex451]

Since BidBatcher is owned by the bidengine.service, we communicate with it by the channel, in this case we can have concurrent orders and one bidBatcher.