TTTA-HUB 22: Add User Permission to Unlock Approved Reports

[AdamAdHocTeam]

Description of change

Added new global param to allow select users to UNLOCK approved reports.

How to test

Enable the new UNLOCK global user param on your user. Then create a new report and approve. When viewing the approved report you should now see the UNLOCK button. Clicking this button and agreeing to unlock should set the report and all approvers back to a NEEDS_ACTION state.

Issue(s)

• https://ocio-jira.acf.hhs.gov/browse/TTAHUB-22

Checklists

Every PR

• Meets issue criteria
• JIRA ticket status updated
• Code is meaningfully tested
• Meets accessibility standards (WCAG 2.1 Levels A, AA)
  - [ ] API Documentation updated
  - [ ] Boundary diagram updated
  - [ ] Logical Data Model updated
  - [ ] Architectural Decision Records written for major infrastructure decisions

Production Deploy

- [ ] Staging smoke test completed

After merge/deploy

• Update JIRA ticket status

[thewatermethod]

I understand it might be out of scope of this PR to handle all the accessibility issues with our modals, but I would at least like to see

• "Copy URL Link" & "Print PDF" disabled when the modal is open. I will probably open a Jira for handling modal related issues keyboard navigation as far the sidebar links, etc
• Probably some expectation setting via an aria-label that the button will reload the page if you do unlock an approved report
• Focus jumps right to cancel when you open the window, which is good, and I think the page reloading when you click "Unlock approved report" will handle that focus management. However, when you pick cancel, ideally focus would be returned to that button.

[thewatermethod]

Looks good! Just a few minor things

[jasalisbury]

I understand it might be out of scope of this PR to handle all the accessibility issues with our modals, but I would at least like to see

• "Copy URL Link" & "Print PDF" disabled when the modal is open. I will probably open a Jira for handling modal related issues keyboard navigation as far the sidebar links, etc
• Probably some expectation setting via an aria-label that the button will reload the page if you do unlock an approved report
• Focus jumps right to cancel when you open the window, which is good, and I think the page reloading when you click "Unlock approved report" will handle that focus management. However, when you pick cancel, ideally focus would be returned to that button.

Playing with USWDS modals here, the focus is trapped inside the modal and the modal closes when I click out. This makes me wonder, 1) Are we using the react-uswds modal correctly? 2) Do we need to update the react-uswds package so our modals act the same as their example?

[jasalisbury]

Looks good! Only have one comment. Also can you add the new route to the API documentation at docs/openapi?

[AdamAdHocTeam]

Looks good! Only have one comment. Also can you add the new route to the API documentation at docs/openapi?

This has been updated.