Log lite - import job summary page, from landing page

Purpose: To provide a lite summary for an individual job; will be refined in a future feature UXPROD-2200

As a staff person importing files via Data Import
I want to see a summary of the actions taken for the records in the file
So that I can be aware of successful imports and errors

Scenarios

1. Scenario 1
   • Given the Data Import landing page
   • When a user clicks on a file name in the list of completed jobs
   • Then take them to a new individual job summary page (instead of opening the MARC JSON log, like happens now)
   • Note that there is a parallel story for when the View all page is the starting point; see UIDATIMP-762
2. Scenario 2
   • Given the Individual job summary page
   • When viewing it
   • Then format as follows
     • Full screen MCL list (a first pane for searching/filtering will be added later)
     • Heading
       • Data import icon
       • Followed by the file name
     • Subheading
       • Total number of records in the incoming file, in the format "x records found" NOTE: Continue to get this number from wherever we get it now; do not get it by totaling the number of rows in the list; that will lead to inaccurate counts
     • Columns
       • Record
         • The number of the record in the file
         • Default sort is ascending by this column, but should be able to switch to descending by clicking the column header
       • Title
         • From the MARC 245 $a field
         • And allow for ascending/descending sort when the column header is clicked
         • Note that when we start loading EDIFACT files, we will need to specify a different field from which to pull the title
       • Columns for each of the following record types, in this order (and allowing ascending/descending sort when the column header is clicked)
         • SRS MARC Bib
         • Instance
         • Holdings
         • Item
         • Order
         • Invoice
         • Error
         • NOTES: Values for these columns are in a separate story. See UIDATIMP-??
3. Scenario 3
   • Ensure this story passes Accessibility testing
4. Scenario 4
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot