feat(providers): add connect_builtin example

[yash-atreya]

• Updates the dependencies in examples-providers.
• Adds the connect_builtin examples for all three builtin transport type. HTTP, WS and IPC.

[yash-atreya]

This would fail ci due to the IPC path not being present.

[mattsse]

does this work locally?

it's possible that the file is created somewhere else, I think we want this as a getter on the anvil instance as well

[prestwich]

think we want this as a getter on the anvil instance as well

prefer the opposite. ProviderBuilder::on_anvil(self, AnvilSettings)

reasoning: node-bindings is nearly dep-free. we want provider to depend on it, not vice versa

[yash-atreya]

does this work locally?

it's possible that the file is created somewhere else, I think we want this as a getter on the anvil instance as well

It works if the file exists but would ultimately fail with Socket operation on non-socket (os error 38). Because after all, it's not a socket.

[zerosnacks]

This would CI fail due to the IPC path not being present.

If you have an example that cannot be ran (see #31) you can update the filter applied in the CI here:

examples/.github/workflows/test.yml

Lines 44 to 55 in 60d14df

	export examples="$(
	cargo run --example 2>&1 \
	| grep -E '^ ' \
	| grep -v \
	-e 'trezor_signer' \
	-e 'ledger_signer' \
	-e 'yubi_signer' \
	-e 'ipc' \
	-e 'ws' \
	-e 'ws_auth' \
	| xargs -n1 echo
	)"

and here:

examples/.github/workflows/integration.yml

Lines 25 to 37 in 60d14df

	# Get the list of runable examples
	export examples="$(
	cargo run --example 2>&1 \
	| grep -E '^ ' \
	| grep -v \
	-e 'trezor_signer' \
	-e 'ledger_signer' \
	-e 'yubi_signer' \
	-e 'ipc' \
	-e 'ws' \
	-e 'ws_auth' \
	| xargs -n1 echo
	)"

[zerosnacks]

More of a general comment and a personal opinion but I'm not a fan of the connect_builtin name. I don't think it is particularly clear to users and sounds like an internal method rather than the equivalent of a default.

[zerosnacks]

Possibly beyond the scope of the intended PR but I would also prefer to see the parameter being strongly typed (Url-like) instead of a &str

[zerosnacks]

Why are these required and not accessible on the alloy namespace?

[yash-atreya]

Compiler doesn't the recognize them as the same type when used with alloy-provider (w/o the namespace). Ref: #26

[zerosnacks]

Ah I see, then this should be resolved once that upstream PR has been merged

[mattsse]

lgtm, pending CI filter