Stop sending reviewer_data in the recommend_reviewers flow

What does this merge request do and why?

The recommend_reviewers flow sent the same reviewer data two times, under the reviewer_data and agent_platform_recommend_reviewers_context context categories. Flow 3.0.0 in the Duo Workflow Service reads only agent_platform_recommend_reviewers_context. It skips categories that the flow config does not declare, so the reviewer_data copy never got to the model.

The two copies made DUO_WORKFLOW_ADDITIONAL_CONTEXT_CONTENT too large for some merge requests, and the workload jobs failed with dumb-init: argument list too long. This change sends one copy, which halves the size of the reviewer data. The data that the model gets does not change.

References

#630285

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.