fix: disable rust-proto-check in ci (#1898)

#1436  was merged despite the test it added not actually being ran by CI
This has prevented the CI test suit from running completely since.

This didn't trigger the workflow to have a non-zero exit code as the
eval commands were spawned asynchronously. Their stderr and exit codes
were disregarded while what did stream from their stdout was captured by
files used to continue the rest of the workflow.

These commands in unionlabs/workflows should be ran in a way that their
exit status is reflected in the parent and the currently failing test
that are in main should be fixed.

The following 13 enabled test are currently failing:
- `.#checks.x86_64-linux.arbitrum-light-client-tests`
- `.#checks.x86_64-linux.biome-lint`
- `.#checks.x86_64-linux.cometbls-light-client-tests`
- `.#checks.x86_64-linux.ethereum-light-client-mainnet-tests`
- `.#checks.x86_64-linux.ethereum-light-client-minimal-tests`
- `.#checks.x86_64-linux.ethereum-verifier-clippy`
- `.#checks.x86_64-linux.ethereum-verifier-tests`
- `.#checks.x86_64-linux.go-staticcheck`
- `.#checks.x86_64-linux.scroll-light-client-tests`
- `.#checks.x86_64-linux.tendermint-light-client-tests`
- `.#checks.x86_64-linux.ucs00-pingpong-tests`
- `.#checks.x86_64-linux.ucs01-relay-tests`
- `.#checks.x86_64-linux.ucs02-nft-tests`