Receiving history: item barcode, location and status

Purpose:
According to UIREC-2

Update Item Details
...
The Barcode, Location, and item status will be retrieved from inventory for each item displayed
...

Current state:
UI consumes GET /orders/receiving-history endpoint as an entry point for receiving flow. mod-orders uses receiving_history.json schema from mod-orders-storage which does not have (and should not) item's information other than id.

Required updates:
Introduce separate receiving history schema for mod-orders and include optional properties related to inventory item content:

• barcode
• location
• status

Once the information is got from orders storage, mod-orders should make separate calls to inventory to get required information.

The mod-inventory item.json schema has 3 properties representing locations:

• permanentLocation
• temporaryLocation
• effectiveLocation

According to the description in the schema looks like the effectiveLocation is the best one to rely on. Alternative option is to make separate call to holdings by holdingsRecordId to get location id.