Create the primary search options for Order lines

Overview: Until the PO/POL search results can be displayed in a hierarchical view, we will show the PO and POL search results separately. This story describes the search options for POLs that are most urgent to implement. Secondary, less-urgent options are described in UIOR-264. Users need the ability to search and filter orders 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.

There is a column in this Google sheet marked Searchable (column H) which identifies the fields that should appear as search options. There is a tab for each App so you will need to navigate to the "Order" tab in this sheet for Order fields, and only pay attention to the green search options for the POL, not the yellow or the PO. https://docs.google.com/spreadsheets/d/1F88PoSnEKD7oFnza1ZuOgzAgKnK95XOyTQzxyww3tZA/edit#gid=1408113181https://docs.google.com/spreadsheets/d/1F88PoSnEKD7oFnza1ZuOgzAgKnK95XOyTQzxyww3tZA/edit#gid=1408113181

1. Scenario 1
   • Given the Orders app landing page
   • When a user wants to search within POLs (the purchase order line toggle is highlighted)
   • Then they should see the following options in the search dropdown list, in this order:
     • Keyword (includes Title , Contributor , Product ID , PO line number , Requester , Vendor account , Vendor reference number )
       • NOTE: Ensure this search will also allow (Title + Contributor) keyword searching, e.g. History Smith; this is broken out as a separate story; see UIOR-273
     • Contributor
     • PO line number
     • Product ID (see separate story UIOR-274 for normalizing ISBNs for searching)
     • Product ID should currently search all product IDs in the records. Please fix
     • Requester
     • Title
     • Title + Contributor (this is broken out to separate story, use UIOR-273)
     • Vendor account
     • Vendor reference number
   • And results should be displayed as indicated in UIOR-270
2. Scenario 2
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot