replace alloy dependencies with specific sub-dependencies

[MartinquaXD]

Description

While depending on alloy is convenient because it bundles everything inside 1 dependency it also hides what parts are actually needed and can delay the compilation of crates unnecessarily.

Changes

replace alloy dependency with the actually used sub-crates like alloy-primitives and alloy-provider

this PR mostly focuses on the smaller "leaf" dependency crates as they are manageable in size and allowing them to compile earlier is more important than optimizing crates like driver, and autopilot.

So far this PR only improves the compile time very slightly by making sure contracts does not indirectly depend on aws-sdk-kms as that is insanely slow to compile.
The effects of this change will be more pronounced when we change the contracts crate to be compiled as individual crates.
But I think even without huge compile time gains being explicit about our dependencies still makes sense.

How to test

compiler

[gemini-code-assist]

Code Review

This pull request effectively refactors the dependency on the monolithic alloy crate into more granular sub-crate dependencies. This is a positive change for dependency management and should help with compile times. The extraction of signature-validator and zeroex_api from the shared crate into their own crates is also a good step towards better modularity. The changes are mostly mechanical and look correct. I have one minor suggestion for improvement.

I am having trouble creating individual review comments. Click here to see my feedback.

crates/liquidity-sources/src/zeroex.rs (66)

The url crate provides a join method that is more robust for joining URL paths than the custom join_url helper. Using it is more idiomatic. After this change, the join_url function can be removed.

        let mut url = base_url.join("/orderbook/v1/orders").unwrap();