[Suggestion] Change nonce field to be u64 compatible

[zerosnacks]

Component

provider, pubsub

Describe the feature you would like

Instead of .nonce(U64::from(1)) we would want to be able to do just .nonce(1).

See: alloy-rs/examples#2 (comment)
See: alloy-rs/examples#2 (comment)
See: alloy-rs/examples#8 (comment)

There are likely also other places where similar user facing values are desired to be native types:

• chain_id
• transaction_type
• etc..

See: alloy-rs/examples#2 (comment)

Additional context

Once implemented make sure to fix in examples: alloy-rs/examples#2

There is some complexity around this, FWD from @prestwich in alloy-rs/examples#8 (comment):

rpc types must store nonce as U64 (or use a serde(with = ...)) to be on-spec so this probably propagates outward from there 😮‍💨 we should settle on a specific type for these and audit codeplace for compliance. prefer u64 in all non-rpc structs

[mattsse]

yeah, we def want this, because usually the input is primitive u64, and it's easier to go form U64 to u64

[zerosnacks]

yeah, we def want this, because usually the input is primitive u64, and it's easier to go form U64 to u64

Added an initial implementation here: #341, uses the u64_hex_or_decimal / u64_hex_or_decimal_opt functions to handle the RPC structs