Rerun deployment once on.converted_to_draft PRs are on.ready_for_review

[CodeGat]

Background

We currently loosen restrictions on Draft PRs as they have no intention of being merged. However, there is an edge case where a draft PR is committed to, passes the loosened restrictions, then converts to Ready For Review. There is a possibility that this is approved and then is merged, which would then later fail the Release Deployment Checks. This would lead to a revert operation in which we must delete the created tag, reset main to HEAD~1, and reopen the merged PR again.

If we require a deployment on.ready_for_review, we would at least see in the checks that there was a failure using the more restrictive checks, if we were looking to merge this into a Release.

Thanks @aidanheerdegen for the suggestion!

[CodeGat]

We would probably hope to bundle this relatively small change in with a larger version:MAJOR change, to lessen the burden on model-deployment repositories.