[Due for payment 2025-05-20] [Simplified Action] Add Review Duplicate to the expense report level

[luacmartins]

Coming from the design doc, we should add Review duplicate as a primary action on the expense report level in addition to the transaction thread

Approvers find it confusing to have to exclusively review expense duplicates at the expense-level, so we'll also show the Review duplicates action to the report level. Again, this adds consistency with other warn violation cases.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.44-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Add review duplicates to report level #61273

If no regressions arise, payment will be issued on 2025-05-20. 🎊

For reference, here are some details about the assignees on this issue:

• @c3024 requires payment through NewDot Manual Requests

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.