Added debug information for decision timeout handling

[3vilhamster]

What changed?
I've aded a metric dimension for decision type timeout metric.
Also, added a domain name tag to the log message that can allow stakeholders debugging issues.

Why?
To provide stakeholders runbook to handle schedule_to_start events

How did you test it?
Unit tests.

Potential risks
For huge clusters with a lot of domains and a lot of workflow types, metric dimension can cause increase in cardinality.

Release notes
Added debug information for decision schedule_to_start.

Documentation Changes

[taylanisikdemir]

Did you run it locally to check emitted metrics?

[coveralls]

Pull Request Test Coverage Report for Build 018dcc26-903b-4401-abf3-7131aa2dd918

Details

• -8 of 31 (74.19%) changed or added relevant lines in 1 file are covered.
• 42 unchanged lines in 10 files lost coverage.
• Overall coverage increased (+0.01%) to 62.779%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
service/history/task/timer_active_task_executor.go	23	31	74.19%

Files with Coverage Reduction	New Missed Lines	%
service/history/execution/mutable_state_task_refresher.go	1	73.42%
common/task/fifo_task_scheduler.go	2	87.63%
common/task/parallel_task_processor.go	2	93.06%
service/history/task/transfer_standby_task_executor.go	2	87.42%
service/matching/matcher.go	2	90.72%
service/matching/taskListManager.go	2	79.7%
service/history/queue/timer_gate.go	3	95.83%
service/history/queue/timer_queue_processor_base.go	3	77.82%
service/frontend/api/handler.go	5	62.11%
service/history/task/task_util.go	20	70.57%

Totals
Change from base Build 018dc926-14ca-4ed7-82ff-93d34d582624:	0.01%
Covered Lines:	92722
Relevant Lines:	147695

---

💛 - Coveralls