Do not preprocess COW AMMs when not configured

[squadgazzz]

Description

When the driver's COW AMM config is empty, the corresponding task still tries to search for surplus capturing jit order owners among the AMMs and fires a redundant warning log in that case. When the driver doesn't expect any AMMs, this log doesn't make any sense. This PR fixes this.

Changes

• Make the COW AMM cache optional based on the COW AMMs config.
• When None, return fast with no AMMs for every auction with no redundant logs.

How to test

Logs on chains where COW AMMs are not configured.

Related Issues

Fixes #3890

[Copilot]

Pull request overview

This PR optimizes the COW AMM preprocessing flow by making the COW AMM cache optional when no COW AMMs are configured. This prevents unnecessary processing and eliminates spurious warning logs on chains where COW AMMs are not expected.

• Modified Cache::new to return Option<Self>, returning None when factory mappings are empty
• Made cow_amm_cache field optional in preprocessing utilities
• Added early return in cow_amm_orders method when cache is not configured

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
crates/driver/src/domain/cow_amm.rs	Modified Cache::new to return Option<Self>, returning None when no factory mappings are configured
crates/driver/src/domain/competition/pre_processing.rs	Changed cow_amm_cache field to Option<cow_amm::Cache> and added early return logic in cow_amm_orders to handle unconfigured scenarios

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.