proactive logging for some critical events

Its been observed during many CBSEs that the cbcollect that we get is after the service restart and has no useful information. One way to have more debuggability is to add  proactive logging for some critical events and dump of goroutines.

E.g upon detection of conditions such as flush stuck over a threshold amount of time we can have goroutines dump which will help analyze why flush was stuck.

We will add more such conditions here where we would like to have better debuggability.

E.g CBSE where this would have been useful is CBSE-10970