Skip automatic Duo Code Review without flow pipeline access

What does this merge request do and why?

Automatic Duo Code Review runs the Code Review Flow as the merge request author, and the flow creates a pipeline in the target project. When the author does not have create_duo_workflow_for_ci, the flow fails with a DCR4003 error note. With review on push, that note comes back on every push.

The automatic triggers (create, draft to ready, and push) now skip the review, and log the skip, when the author cannot create that pipeline. This applies to:

• Community contributors on fork merge requests.
• Project members below the Developer role.
• Members below the namespace's minimum access level for async flows.

Classic mode and manual review requests do not change. A manual request runs as the user who requests it.

References

#624918 (closed)

Screenshots or screen recordings

Before	After

Merge request acceptance checklist

Evaluate this merge request against the merge request acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.