Fix flaky MaestroWorkflowDaoTest properties updates

[akashdw]

Pull Request type

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes (Please run ./gradlew build --write-locks to refresh dependencies)
• Other (please describe):

Changes in this PR

MaestroWorkflowDaoTest fails intermittently with

duplicate key value violates unique constraint "maestro_workflow_properties_pkey"
Detail: Key (workflow_id, create_time)=(sample-active-wf-with-triggers, 1787704031240) already exists.

maestro_workflow_properties is keyed on (workflow_id, create_time) and updateWorkflowProperties fills create_time from System.currentTimeMillis(), so two updates on the same workflow inside one millisecond collide. Four tests call it repeatedly on one workflow with almost nothing in between, and on a fast machine two of the calls share a millisecond.

Those calls now go through a test helper that sleeps a millisecond first. No production change.

[praneethy91]

maestro_workflow_properties is keyed on (workflow_id, create_time) - pretty unfortunate, would have liked if it was a monotonic key instead but I know that's out of scope for this PR

[akashdw]

agreed, the timestamp in the key is the real problem and the sleep only hides it in tests. I'll think more on adding the monotonic version column in a backward compatible way.