Inventory search. Create filter options for Instance segment

Overview: Until the Instance > Holdings > Item search results can be displayed in a hierarchical view - long term solution defined by () then we'll show the search result defined as is (MVP). A short term solution will be to improve the MCL Result list () - which didn't make it for `cap-mvp`.
Only the filters marked as bold it to be implemented for the MVP.

This story describes the filter options for Instance - and will be a refinement of the existing filters.

Usecase: Circulation staff, catalogers and other staff members need the ability to search and filter Instance records by a number of different field values. This will help them find exactly what they are looking for and what they should be working with.

Scenarios:

1. Scenario

   • Login to FOLIO Snapshot, go to the Inventory app landing page

   • When a user wants to filter within Instance records (the Instance record toggle is highlighted) - as defined in UIIN-758

   • Then they should see the following options in the filters area, in this order:

     • Effective location – implementation see:

     • Permanent location – implementation see: UIIN-679

     • Language – implementation see: UIIN-735

     • Resource type – implemented as one long list. Refined implementation using render filters (same as the Orders App) see:

     • Format – implementation using render filters (same as the Orders App) see: UIIN-820. Longterm we'll implement hierarchical display (, )

     • Mode of issuance

     • Nature of content

     • Classification type

     • Contributor type

     • Publication date (year range) – to be implemented later, see: (not MVP)

     • Previous held (yes) – implementation see:

     • Staff suppress (yes) – only visible if you have the permission to view records marked as Staff suppress (UIIN-746) – implementation see:

     • Suppress from discovery (yes) – implementation see:

     • Mark for delete – implementation see:

     • Date created (date range) – implementation see: UIIN-788

     • Date updated (date range) – implementation see: UIIN-790

     • Created by – to be implemented later (when we can ensure this to be suppressed from the UI by the European libraries according to GDPR, Employment agreement)

     • Updated by – to be implemented later (when we can ensure this to be suppressed from the UI by the European libraries according to GDPR, Employment agreement)

     • Statistical code – implementation see: UIIN-792

     • Instance status – implementation see: UIIN-1207

     • Source – implementation see: UIIN-1132

     • Tags – implementation see: , , UIIN-763

   • And all filter accordions should be closed except for Effective location (set in the Item record)

   • And results should be displayed as is for now until we can get this refined (, and later )

2. Scenario

   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

NOTE Filtering by tags is also high priority for Chalmers, but cannot be implemented until assigning tags to instance records has been implemented. See separate stories , and UIIN-763 for adding filtering by tags.