As a user I want to certify that I am the one allowed to file on the review page

## Description:
Given the basic user is logged in and can pay
When the user makes changes to their filing and wants to pay
Then the user will see a review button, press it and will see the changes the user made and have a place to put their name and click a certify with a statement in the design.
Then the user can only press file and pay after the certify button is engaged

Review should show directors ceased, added.

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed
- [ ] What are the dependencies
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required

Acceptance / DoD:
- [ ] Design / Solution accepted by Product Owner
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed

Start by locating the review page and the filing/payment flow, then confirm the approved design, dependencies, validation rules, and sad paths because the issue leaves these open. Done means the review shows added and ceased directors, provides the certification statement and name entry, and prevents filing and payment until certification is engaged, with acceptable test and accessibility coverage.

Written by the indexing model from the issue text.