Re-introduce automated unit testing (from 647)

[gigamorph]

Problem Description: The backend's automated unit tests were ignored during the last three or so weeks leading up to the Beta 1 release on 20 Oct (v1.0.6). Many, many changes were made that have likely left these as a hot mess. We should get them going again, unless directed to abandon them (Eek!!). Providing we may proceed, there could be done in phases:

1. Comment out broken tests in order to get some working sooner.
2. Delete tests that have become invalid. Includes when the code they test no longer exists or the tests are considered beyond repair.
3. Fix remaining broken tests --that are deemed important enough; discard the rest.
4. Assess for coverage gaps. Prioritize. Write new tests for the most important gaps.

Expected Behavior/Solution: TBD

Requirements: TBD

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

- [ ] Wireframe/Mockup - Heather - [ ] Committee discussions - Sarah

• [ ] Feasibility/Team discussion - Sarah
• [ ] Backend requirements - TBD
• [ ] Frontend requirements- TBD
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• Example endpoints from LUX to use for development and testing, if applicable.

Dependencies/Blocks:

• Blocked By: https://git.yale.edu/lux-its/marklogic/issues/653

Related Github Issues:

• Issues that contain similar work but are not blocking or being blocked by the current issue.

Related links:

Wireframe/Mockup:

[roamye]

@clarkepeterf this issue is no longer blocked as https://git.yale.edu/lux-its/marklogic/issues/653 was closed. Would you please add the req/solution/UAT examples so the issue can move to prioritization review?