Add availabilityConstraints to packages

Purpose:

Some e-resource packages are only available to a limited list of organisations/consortia/regions. This story is to add support for a list of values to a package in order to be able to record such a list of bodies/regions that can use the package, and populate that information when loading JSON package data or harvesting data from GOKb.

Requirements
It should be possible to store the following additional information about packages in Agreements KB

• availabilityConstraints
  • each package can have zero to many availabilityConstraints
  • each availabilityConstraints is a named organisation, consortia or region. No further information is currently required about the body beyond the name

The availabilityConstraints should be populated during JSON package ingest as part of this story. A separate story (ERM-2307) covers population when harvesting from GOKb

This should be the same pattern as the existing packageContentType

Add the property to the schema/ingest service so that JSON ingest includes this new property

Outstanding issues:

• Check normalisation of incoming string when creating refdata value