PAY - Refund UI - move refunds from the lab ops team to business staff

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2025-03-21. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjI4MDY0)._

Today, refunds follow this pattern:
1. Client requests refund
2. Business unit vets request and approves/declines
3. IT Ops cuts a ticket for dev ops team in cases where the refund is ok'ed by the business
4. dev ops team refunds the transaction using the Pay Team's Refund API
5. Ops teams trickle info back to the client when the process is complete

Adding a UI for this process could have the following benefits:
1. Specific roles can be defined per product for requesting and approving refunds
2. Staff can action refunds without delays caused by ticket/ops process
3. Staff have a single place to see the status of their latest refunds
4. SBC Finance can ensure that only EAs are approving refunds - meeting core policy

Assumptions:
1. We should build this into the existing "Transaction Records" section of the Staff Dashboard
2. We should borrow elements from the existing dev ops refunds UI
3. Partial refunds for all payment methods should be considered at the same time, though not a direct dependency
4. We should consider adding an option to refund OB and PAD via cheque in cases where the client doesn't want a credit. (Could become another epic)
5. Related but not a dependency - Consider refunding PAD to the client's bank info (via generic supplier record)

Start with the Staff Dashboard’s Transaction Records section and compare it with the existing dev ops refunds UI; trace the Pay Team’s Refund API to understand the available operations. Done means staff can request, approve, execute, and track refunds with product-specific roles, while supporting the stated partial-refund considerations.

Written by the indexing model from the issue text.