[dup] Gyr1 971 automatically update document type label if screener agrees with assessment 2

[DrewProebstelCfa]

Link to pivotal/JIRA issue

• e.g. https://codeforamerica.atlassian.net/browse/ABCD-123

Is PM acceptance required? (delete one)

• Yes - don't merge until JIRA issue is accepted!
• No - merge after code review approval

Reminder: merge main into this branch and get green tests before merging to main

What was done?

• Explain the implementation goals being solved or the feature with the reviewer in mind
• Mention any relevant issues or insights to be shared with the reviewer.
• Alternatives considered

How to test?

• Describe the testing approach taken to verify the changes, including:
  • Unit/integration/manual tests
  • Test data used
• Specify any relevant testing environments used (e.g., development, staging, demo, Heroku).
• Risk Assessment
  • Risks or side effects associated with the changes and how they were mitigated.
  • Highlight areas that may need extra attention during code review or testing.
  • Paste SQL queries or output where relevant

Screenshots (for visual changes)

• Before
• After

[github-actions]

Heroku app: https://gyr-review-app-6253-fbf225851e10.herokuapp.com/
View logs: heroku logs --app gyr-review-app-6253 (optionally add --tail)