Fix patient issue list to reflect new reports

[johnny2smooth]

Description

This to-do was raised to make sure that patient issue data was being updated more often than daily, if a patient ended up having an issue after the initial list was created resolved.

To-do

• Modify alreadyReviewed logic on front end to further specify requirements
• instead of checking wasToday we can check that this last general resolution was created after their last report.
• Add logic (+maybe other checks) to verify there aren't any new reports since last general resolution
• Sync up logic with current components and
• unresolvedReports.createdAt time is not changing! even when a new update + message is made
• Reviewed patient with initial problem repopulates to unreviewed upon reload.
• Rename ^^ and refactor

Screenshots

Upon patient resolution, the resolutions API is updated. It is being sent twice as an OPTIONS and a POST method.

Notice here how there is no API request to update the list of patient_issues.

When this page is reloaded, we see that all of the original patient_issues data is being sent. None of the previous interactions have changed its shape.

I am curious as to how the page knows how to not render all the issues from the API

New understanding