Invoice/Invoice-line schema updates

Overview:
This is a catch-all story for making schema changes to the invoice and invoice-line schemas, examples, and sample data (if applicable)

Invoice

• add lockTotal (boolean) - not required. Default: false
• add adjustments - array of adjustment objects - not required
• add adjustmentsTotal (decimal)
• rename totalAmount -> total
• add subTotal (decimal) - invoice total before adjustments are applied
• remove prorata
• rename owner -> acquisitionsUnit

Invoice Line

Remove the following fields:

• reportTax
• invoiceLineTax
• pieceIds

Update the following:

• add subTotal (decimal) - required
• add adjustmentsTotal (decimal)
• rename price -> total
• rename adjustmentsFieldSet -> adjustments
• rename doNotReleaseEncumbrance -> releaseEncumbrance. Default: true
• rename poLineIds -> poLineId changing type array to string (invoice line can be linked to only one PO line)
• fundDistributions to be and array of fund_distribution objects (currently an array of string)
  • Copy the https://github.com/folio-org/acq-models/blob/master/mod-orders-storage/schemas/fund_distribution.json schema to the mod-invoice-storage area and make the following edits:
  • Add fundId - UUID of the fund - required
  • Make code optional
  • Add invoiceLineId - UUID of the invoiceLine associated with this fund distribution - optional

These changes will also be made to the orders version but this will be handled in a separate story (MODORDERS-242).

NOTE Eventually we might have orders/invoicing share a single fund_distribution schema, but for now we keep them separate until we're sure there aren't any good reasons why they can't be combined. There's also a fund_distribution schema in mod-finance that could factor into this as well.

See Acquisitions Interface Fields for details

Acceptance Criteria:

• Schemas have been updated as described above
• Example data has been updated
• Unit and API tests have been updated as needed