ScanReportTable Jobs Overview

[blargly]

Mapping a scan report now has distinct stages of worker functions that happen sequentially:

• run upload
• select person/date
• triggers the reuse
• triggers the rules

We need to make the visibility clearer, as these jobs are long running, can fail, and the user currently has no visibility over what us happening.

[!WARNING] See the whiteboard for the concepts / design / UI: https://whiteboard.office.com/me/whiteboards/p/c3BvOmh0dHBzOi8vdW5pb2Zub3R0bS1teS5zaGFyZXBvaW50LmNvbS9wZXJzb25hbC9hbmR5X3JhZV9ub3R0aW5naGFtX2FjX3Vr/b!mAc72Dvk6UuVmxWuetQtl8zmGUHZCmRMuk2mkR3EwGnrX1IFgGvfTomSDAHImloJ/01BCY66MB2W4C3TFKKGRHIT7W46NBRD3B5

Rough plan / thoughts:

• Update status in a SR list view be a link to a Status Overview page
• This might look a bit like Github actions page - display a list of Jobs (which are the stages), showing the path and the order which has to occur.
• Successful Jobs will have a green tick - a yellow mark for warnings (?) and a red exclamation for failure.
• Ideally have some log information detailing errors for the user to see.
• As the jobs occur on one table, this is a list of the Scan Report tables, with "Jobs" that have been run at each stage against them.
• One Scan Report Stage can have multiple Jobs run against it.
• Details page can also link to this, and allow you to look at every stages information/logging details
• Users could be notified when a Job has changed status.

Tasks:

• [ ] #696
• [ ] #743
• [ ] #744
• [ ] #745
• [ ] #746
• [ ] #747