Service document should support advertising min and max segment sizes

[alexdutton]

Invenio has min and max part size limits, which will also apply to the invenio-sword segmented upload deposit implementation.

At the moment, invenio-sword will reject segment-init requests outside of these limits with a ValidationError, but it has no standardised way to advertise the requirements for clients to follow.

Can we add optional minSegmentSize and maxSegmentSize attributes to the service document?

[richard-jones]

Notes on implementation:

• add to the example json document

• add to the json schema

• Add a error types for exceeding/not meeting these requirements

• Update description of usage in 16.4

• Update description of errors in 16.9

[alexdutton]

Have these changes been published to GitHub Pages? I can't see any new properties at https://swordapp.github.io/swordv3/service-document.schema.json …