Handle poor performing eth1 data retrieval

[prestonvanloon]

A user reported block proposal failure due to a poor performing eth1 node.

[2020-04-19 16:29:12] ERROR validator: Failed to request block from beacon node blockSlot=14245 error=rpc error: code = Internal desc = Could not get ETH1 data: could not get block number from timestamp: Post "https://goerli.prylabs.net/": context deadline exceeded pubKey=0xa92c463e6c83

The recommended fix here is to set a short timeout for fetching eth1data for eth1data votes, if the short timeout is exceeded then a block should be produced with random/noop eth1data vote such that the proposer can still produce the block in time.