Design for suspended account when CFS validation fails after que

## Description: This is a design ticket for 5440

Scenario 1: Fail validation for bank account in que

GIVEN bank info that was in the que is sent to the CFS
WHEN the bank account fails the validation
THEN the account will temporarily be suspended
AND the user sees the suspended UI on next log in
(image in Figma)
https://www.figma.com/design/BRLFiH8ApQRkrQtfGcRUdn/Relationships?node-id=26435-153&t=04aJvEwYfdb4UL0Q-1

Scenario 2: User changes bank information when CFS is down

GIVEN User changes bank information in suspended UI
(image in Figma)
https://www.figma.com/design/BRLFiH8ApQRkrQtfGcRUdn/Relationships?node-id=26435-153&t=04aJvEwYfdb4UL0Q-1
WHEN users click on "Proceed" when CFS is down
THEN users will see a "account hold" UI
(image in Figma)
https://www.figma.com/design/BRLFiH8ApQRkrQtfGcRUdn/Relationships?node-id=26435-155&t=04aJvEwYfdb4UL0Q-1
AND the user will be able to access their account when CFS validates bank information

Acceptance for a Task:
- [ ] Requires deployments
- [ ] Add/ maintain selectors for QA purposes
- [ ] Test coverage acceptable
- [ ] Linters passed
- [ ] Peer Reviewed
- [ ] PR Accepted
- [ ] Production burn in completed

Start by reviewing issue 5440 and the linked Figma flows for validation failure, suspended accounts, and the CFS-down path. Identify the relevant frontend and account-validation entry points from that work; done means the described states, QA selectors, tests, linting, review, deployment, and production burn-in are completed.

Written by the indexing model from the issue text.