OCTRL-1033 Enhance monitoring with call durations

[justonedev1]

I went over hooks and added call duration monitoring to:

1. hooks in general
2. each callable in hooks
3. every call in plugins that I found valuable - except BKP as it uses kafka now. If you think that I should add monitoring even to BKP plugin I will do so. It is also possible that I missed something.

[justonedev1]

@knopers8 tested, you can review

[justonedev1]

Latest changes:

• I had to regenerate all protofiles as grpc generated with new enough protoc contain routing name inside the grpc file instead of piecing it together myself. As a part of this I regenerated everything as our grpc files are generated with hodgepodge of protocs. I can move this to different PR if you want, but it is in it's own unique commit so it doesn't pollute history.
• monitoring is in call.go on 2 places: call.Call() which gives us the most granular measurement of duration possible of each process in whole hook, second place is the call.Start() in goroutine where we measure wrapped Call() function where we can see when call is time outed
• monitoring in all integration plugins except bookkeeping as grpc interceptors
• DCS specific monitoring in grpc streams implemented again as interceptors and also measurement of whole dcs communication

[knopers8]

thank you!