Anvil polling interval

[tuler]

The default polling interval of the viem connection to anvil is the default block time divided by 3, which is 12s / 3 = 4s, which is very long.
The default block time is already being set to 2s.
In a local test environment I think we can set the polling interval to a very low value, so the send operations are faster.
I'm setting here to 200ms, which makes the average time to send an input from more than 8s, to less than 2s.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🟢	Lines	92.96% (🎯 0%)	726 / 781
🔵	Statements	92.96%	726 / 781
🔵	Functions	92.54%	62 / 67
🔵	Branches	0%	0 / 0

📁 File Coverage (11 files)

File	Lines	Statements	Functions	Branches	Uncovered Lines
apps/cli/src/builder/directory.ts	🟢 100%	🟢 100%	🟢 100%	🔴 0%	-
apps/cli/src/builder/docker.ts	🟢 88.68%	🟢 88.68%	🟡 75%	🔴 0%	83-85, 139-147
apps/cli/src/builder/empty.ts	🟢 100%	🟢 100%	🟢 100%	🔴 0%	-
apps/cli/src/builder/none.ts	🟢 100%	🟢 100%	🟢 100%	🔴 0%	-
apps/cli/src/builder/tar.ts	🟢 100%	🟢 100%	🟢 100%	🔴 0%	-
apps/cli/src/config.ts	🟢 92.63%	🟢 92.63%	🟢 94.12%	🔴 0%	65-66, 217, 226, 235, 255, ...
apps/cli/src/exec/cartesi-machine.ts	🟡 75%	🟡 75%	🟡 66.67%	🔴 0%	10-12, 28-30
apps/cli/src/exec/genext2fs.ts	🟢 96.92%	🟢 96.92%	🟢 100%	🔴 0%	87-88
apps/cli/src/exec/index.ts	🟢 100%	🟢 100%	🟢 100%	🔴 0%	-
apps/cli/src/exec/mksquashfs.ts	🟢 91.23%	🟢 91.23%	🟢 100%	🔴 0%	68-72
apps/cli/src/exec/util.ts	🟢 94.44%	🟢 94.44%	🟢 100%	🔴 0%	47-48

[brunomenezes]

For DevNet, I think it's a no-brainer. Would Anvil support websockets? I am not sure if that would be faster, though.

[tuler]

Would Anvil support websockets? I am not sure if that would be faster, though.

Anvil does support WebSocket, but I tried to use it right now and it didn't work.
It may be because we have a traefik proxy between the host and the docker anvil service, that may need special configuration for WebSocket.

I'll merge as is, and investigate that in the future.

[tuler]

It may be because we have a traefik proxy between the host and the docker anvil service, that may need special configuration for WebSocket.

According to traefik docs it should be automatic, so I don't think it's Traefik's fault.

Traefik Proxy supports WebSocket (WS) and WebSocket Secure (WSS) connections out of the box. No special configuration is required beyond standard HTTP routing.

[tuler]

Opened a separate draft for WebSocket connection
#419