863 - Retry a DSR (FE)

[chriscalhoun1974]

Purpose

Can reprocess from the BE, but need to provide ability to do so from FE.

Acceptance Criteria

Demonstrate that a user can retry an ERRORED subject request from the UI
retry should not be supported on other SR states (i.e. New, in progress, completed, etc)

Changes

Added Retry button which will only be rendered if the SR record has an Error status. Once the Retry button is clicked and the API endpoint (/privacy-request/{{privacy_request_id}}/retry) returns a successful response, the status is changed to In Processing and the Retry button is no longer rendered. If the API endpoint returns an exception, a toast message is rendered with the API exception message displayed.

Checklist

• Update CHANGELOG.md file
  • Merge in main so the most recent CHANGELOG.md file is being appended to
  • Add description within the Unreleased section in an appropriate category. Add a new category from the list at the top of the file if the needed one isn't already there.
  • Add a link to this PR at the end of the description with the PR number as the text. example: #1
• Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
• If docs updated (select one):
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Good unit test/integration test coverage
• This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
• The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket

Fixes #863

[pattisdr]

This works well @chriscalhoun1974, nice error handling

[pattisdr]

Just the changelog conflict needed

[pattisdr]

Looks good, just existing mssql failures, unrelated to this PR