client-side polling in FSM leads to journal spam in Lotus

[raulk]

The storage client implements a form of polling through the FSM by triggering self-looping ClientEventWaitForDealState events. This polling is done every second in practice. Unfortunately, because these are FSM events, they trigger event subscribers, which in turn ends up writing a journal record on the Lotus side.

Basically, for every inflight storage deal that hasn't yet been accepted, Lotus will write a big log statement every second.

Relevant symbols are:

• waitAgain
• CheckForDealAcceptance
• ClientEventWaitForDealState

We should get rid of this polling-via-the-FSM contraption, and instead just perform the polling through a standard ticker loop goroutine which triggers an event back to the event loop once a condition has been met. This can be started by CheckForDealAcceptance.