UI Design - Improve Indication of Pending Deletion Scenario

Originated from Ops issue, **INC0101112**. When this is designed and a dev ticket created, please add the this ops issue number so we can follow up with staff on the solution.

An NR goes into Pending Deletion status when:
1. Non-staff creates an NR
2. Due to system error, user's payment method failure, or any other reason, NR stays in "Payment Pending"
3. If NR is still in "Payment Pending" by midnight that night, system changes status to "Pending Deletion" (Confirming this with Thor. Maybe we can extend it)
4. The NR stays in "Payment Deletion" for 5 days, waiting to see if the payment ever comes through. (This is the stage that Jenn is seeing, and it is not clear to the client. Maybe we can improve the client's UI here)
5. If the NR's payment does come through, I check with Debbie/Jenn if they have made a replacement yet or not, and if not, we set it to "Draft" state for the client to use (this is rare)
6. If the NR's payment does NOT come through, it gets cancelled.

### Invision
https://projects.invisionapp.com/share/2K11F0EFSP8T

Start with the linked InVision design and review the six-step Pending Deletion workflow in this issue, especially the five-day period that clients find unclear. Confirm the approved UI outcome with the originating Ops issue INC0101112; done should include a development ticket linked to that issue and a client-facing indication that clearly explains the pending-deletion state.

Written by the indexing model from the issue text.