[Wf-Diagnostics] Rootcause issues causing timeouts

[sankari165]

What changed?
Timeout invariant now has a method that provides a list of potential root causes for the identified issues. Pollers and heart beating checks are added to begin with. More rootcause checks will be added in future PRs

Why?
Timeouts are usually caused by missing pollers and activity timeouts specifically could be due to missing heartbeating config. These are checked as potential root causes.

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 20 lines in your changes missing coverage. Please review.

Project coverage is 72.93%. Comparing base (e23c5a6) to head (e9d003c).
Report is 4 commits behind head on master.

Files	Patch %	Lines
service/worker/diagnostics/invariants/timeout.go	74.64%	11 Missing and 7 partials ⚠️
...ice/worker/diagnostics/invariants/timeout_utils.go	81.81%	2 Missing ⚠️

Additional details and impacted files

Files	Coverage Δ
service/worker/diagnostics/activities.go	100.00% <100.00%> (ø)
service/worker/diagnostics/workflow.go	91.30% <100.00%> (+0.82%)	⬆️
...ice/worker/diagnostics/invariants/timeout_utils.go	81.70% <81.81%> (+0.62%)	⬆️
service/worker/diagnostics/invariants/timeout.go	82.60% <74.64%> (-13.05%)	⬇️

... and 5 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e23c5a6...e9d003c. Read the comment docs.

[dkrotx]

This suppose to hit a lot - lots of activity calls don't use heartbeats.
Are you taking into account it is not as crucial as not the next if-statement?

[sankari165]

there is no prioritisation done here. we simply list potential root causes cos we cant quite predict what suits the usecase. but calling out heart beating not enabled is one of the many observations we return when an activity times out.