Backfill Tests for APIServer

[MbolotSuse]

APIServer currently has limited tests, and the tests that it does have are focused mostly on unit test functionality. This creates a need for highly manual review of things like dependency bumps, and low confidence in the regression potential for changes. These tests should focus on how APIServer would be used as a library and avoid mocking as much as is possible. Some potential examples:

• Create an APIServer. Register a new type.
  • Register a path for the resource using the same "gorrilla/mux" version as the rest of APIServer.
  • Make sure that without resource/collection methods, this isn't accessible to the outside world.
  • Create/update/delete the new type (after adding http verbs to allow access)
• Use APIroot to register more than one collection of schemas, and ensure that the resources of each collection are accessible
• Use Subscribe to add a websocket for the schemas. Ensure create/update/delete events are streamed.
• Use an "AccessControl" struct to allow access to different types of requests (for example, based on userID). Ensure that requests are allowed/rejected as expected.