Outport driver stuck prints

[iulianpascalau]

Description of the reasoning behind the pull request

• Whenever an outport driver gets stuck the node will stop processing new blocks as to disallow dropping information from the chain for each driver. The stop is done without much information in the node's log so any integrator hitting in to this issue will have no clue what it's happening.

Proposed Changes

• added timeout log prints whenever a driver gets stuck

Testing procedure

• standard testing procedure
• start a system testnet, stop an observer, edit the external.toml file enabling the EventNotifierConnector driver without attaching a go notifier and restart the node. The node should stop adding new blocks, after ~30seconds we should have a warning log print stating outport.monitorCompletionOnDriver took too long

[codecov-commenter]

Codecov Report

Merging #4452 (846ff81) into rc/v1.4.0 (b68f53d) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           rc/v1.4.0    #4452      +/-   ##
=============================================
+ Coverage      73.84%   73.85%   +0.01%     
=============================================
  Files            689      689              
  Lines          88122    88153      +31     
=============================================
+ Hits           65070    65103      +33     
+ Misses         18140    18139       -1     
+ Partials        4912     4911       -1     

Impacted Files	Coverage Δ
outport/outport.go	100.00% <100.00%> (ø)
storage/txcache/txListBySenderMap.go	100.00% <0.00%> (+2.50%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[gabi-vuls]

System test passed.