[Bug] Evaluate correctness of BlockNumberOrTag versus BlockId usage in RPC methods

[zerosnacks]

Component

rpc

What version of Alloy are you on?

No response

Operating System

macOS (Intel)

Describe the bug

According to the execution API documentation: https://ethereum.github.io/execution-apis/api-documentation/ it appears that some of the RPC methods support BlockId (the superset incl. block hashes) rather than BlockNumberOrTag (tag + block numbers).

One of them is

alloy/crates/provider/src/provider/trait.rs

Lines 323 to 329 in c3ccf7e

	/// Gets the selected block [BlockNumberOrTag] receipts.
	async fn get_block_receipts(
	&self,
	block: BlockNumberOrTag,
	) -> TransportResult<Option<Vec<N::ReceiptResponse>>> {
	self.client().request("eth_getBlockReceipts", (block,)).await
	}

as flagged in this PR: foundry-rs/foundry#8623

Goal of this ticket would be to go through the RPC methods and evaluate + fix where we can use the BlockId superset over the BlockNumberOrTag.