[Followup] Trait for relationships between receipts, logs, and log contents

We need trait bounds for specifying when the contents of a receipt log vector can be interpreted as logs. I.e. a trait-based definition for what a log is, including encoded, decoded, rpc, consensus, etc.

This means that they contain a `consensus::Log` object (either consensus Log or RPC Log containing an inner consensus log) and that the data type `consensus::Log` can be infallibly converted into `LogData`

it's a bit more complicated and we will need more work here. Because `Log` is actually `Log` we want to be able to implement generically across a wide variety of types, and may need to introduce a `trait Log` in order to do it

For now, this is an improvement over the existing state of things so we might as well

_Originally posted by @prestwich in https://github.com/alloy-rs/alloy/pull/617#discussion_r1577787888_