Maybe: avoid waitForStateComplete workflow getting timeout

Use a timer after workflow start. When the timer fired and signal is not received yet, failed the workflow.

This will help to not get timeout metrics for the namespace.

And also prevent an extremely rare edge case that the workflow will get timeout at the same time of receiving the signal…

However, always starting a timer is expensive…

The best way is to implement the V2 https://github.com/indeedeng/iwf/issues/349

Start with the waitForStateComplete workflow and read the V2 proposal in issue #349. Evaluate the timer-after-start approach, its cost, timeout metrics, and signal race; done requires an agreed implementation that addresses these concerns.

Written by the indexing model from the issue text.