chore: bump alloy 4e22b9e

[fgimenez]

Towards #7702

[mattsse]

great, fewer alloy changes is good

the most significant change was to: Option<TxKind> on the tx request.

this nuance has no impact on the server side and we can always use unwrap_or_default

[onbjerg]

@fgimenez #7885 is being merged which will have a small impact on this PR

[fgimenez]

@fgimenez #7885 is being merged which will have a small impact on this PR

awesome thanks for the heads up!

[fgimenez]

the most significant change was to: Option<TxKind> on the tx request.

this nuance has no impact on the server side and we can always use unwrap_or_default

yep, there were also other minor changes in alloy's serde.

wrt to the new to type in TransactionRequest, we previously had Option<Address> and I assume that None here was interpreted as a create transaction. Now we have Option<TxKind>, we have Some(TxKind::Call(to)) and Some(TxKind::Create), how should we interpret None now? In the changes in this PR None means create too (same as Some(TxCall::Create)), let me know if that's correct.

[onbjerg]

looks sound to me defaulting to create, my nits can be looked at in a follow up

for clarity None means that the user did not specify what they wanted to do with the transaction request and the node should instead infer, the only thing we can probably infer is that it should be a create