Create an eFolder document upload API within vets-api

[srmyers17]

User Story

As a developer, I should be able to upload non-structured documents directly to a Veteran’s eFolder using an endpoint within vets-api.

Acceptance Criteria

• [x] uploaded documents are validated for size and type
• [x] uploaded documents are scanned for viruses
• [x] uploaded documents are processed asynchronously
• [x] the upload service can handle multipart uploads
• [ ] a valid GUID is returned when a document is accepted
• [ ] given a GUID, you can check the status of the upload
• [ ] the upload service implements rate-limiting to protect va.gov services
• [ ] once a document is uploaded to an eFolder, it is deleted from local tmp space/s3
• [x] metrics are gathered on successful and unsuccessful uploads

[jjulian]

Dec 20 update from Eric Buitenhuis:

• The eDocumentService is old legacy and should not be used
• Build against the SOAP services described in the doc
• Only SOAP services are in production as of December 13, 2019

[jjulian]

Jan 16 Peter Karman (caseflow team) says connect_vbms is the most modern way to access VBMS/eFolder.

[jjulian]

Jan 20

• We have reached out to Kristin for access to VBMS.
• Here are the data structures for 530 and 534-EZ from Andrew Cummings.