Flows: pausing holds people in place, and After loop waits for the loop

A full review of the flows engine, and a fix for everything it found.

Things you will notice

• Pause holds people where they are. Pausing a flow used to cancel anyone whose wait ended while it was paused. Now they wait, and carry on when you resume.
• After loop waits for the loop. Steps on a For each step's After loop path run once every item has finished (or after 24 hours), not straight away.
• A wait at the end of a flow ends it. A flow finishing on a wait no longer starts again from the top when the wait is over.
• The Run button works for flows that aren't about a record, straight from the Flows list.
• Testing a step for real says who it will act on before it sends anything.
• Two people editing one flow are told, instead of one silently overwriting the other.

Rules that now apply everywhere

• Enrolment settings (only once, not while already in the flow) apply to form, chatbot, booking and webhook flows, against the record the flow creates or finds.
• People whose record is archived, deleted or merged away leave the flow.
• Conditions no longer treat text like "Plan 1" and "Plan 2" as the same, and date conditions count days in your workspace's timezone.
• Scheduled flows look at every matching record, not just the oldest 500.
• A failed HTTP request follows the step's own error setting, retries only when retrying can help, and data with quotes or line breaks no longer breaks a JSON body.
• An approval can only be answered by the people it was sent to (or an admin), and closes itself if the run ends another way.
• Duplicating a flow copies its goal, unenrolment rules, schedule window, alerts and unpublished changes.