feat(alloy): forward rustls & native reqwest TLS configuration to Alloy's metacrate

[zerosnacks]

Motivation

Closes #965

In support of the suggested feature as people often express their preference for one over the other

Solution

Avoids introducing breaking changes, adds two new flags: reqwest-rustls-tls and reqwest-native-tls

If a breaking change were permitted I would add the flag like this:

alloy/crates/alloy/Cargo.toml

Lines 67 to 103 in 7c1df0f

	[features]
	default = ["std", "reqwest", "reqwest-default-tls"]
	# std
	std = [
	"alloy-core/std",
	"alloy-eips?/std",
	"alloy-genesis?/std",
	"alloy-serde?/std",
	"alloy-consensus?/std",
	]
	# full
	full = [
	"consensus",
	"contract",
	"eips",
	"k256",
	"kzg",
	"network",
	"provider-http", # includes `providers`
	"provider-ws", # includes `providers`
	"provider-ipc", # includes `providers`
	"rpc-types", # includes `rpc-types-eth`
	"signer-local", # includes `signers`
	]
	# configuration
	reqwest = [
	"dep:reqwest",
	"alloy-rpc-client?/reqwest",
	"alloy-provider?/reqwest",
	"alloy-transport-http?/reqwest",
	]
	reqwest-default-tls = ["reqwest", "alloy-transport-http?/reqwest-default-tls"]
	reqwest-rustls-tls = ["reqwest", "alloy-transport-http?/reqwest-rustls-tls"]
	reqwest-native-tls = ["reqwest", "alloy-transport-http?/reqwest-native-tls"]

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes