add timeout when waiting for chiapos to return

[emlowe]

This is likely only a small benefit, but it will log an error sooner and cause a FarmingInfo message to be sent to the farmer when the timeout fires, which is possibly helpful in diagnostics. It also upgrades from a warning to an error in cases where it takes such a long time for the call to return.

I believe the python thread that is "occupied" doing the actual disk lookups via chiapos will continue to be occupied after this timeout, so I don't think this frees the thread to be used by another lookup. That is the thread is still blocked waiting for a chiapos response.

This just allows us to log the error sooner and return a message to the farmer rather than waiting for however long it takes the actual blocking_lookup call to return.

My reading of the overall code is that once all the available threads (default 30) get blocked, your harvester won't be able to process any SPs and they will pile up here as they get scheduled by run_in_executor - possibly there should be some limit set as to how many SPs can get piled up here before we stop doing that. This would need to add in some tracking of the tasks outstanding and if too many, stop scheduling them.

[github-actions]

File	Coverage	Missing Lines
chia/harvester/harvester_api.py	66.7%	lines 264, 275-276, 279-280

Total	Missing	Coverage
15 lines	5 lines	66%

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.