Issue 14

to summarise my changes:

- i created an abstract superclass which factors out any common functionality or properties needed by all of our application's endpoints. things like json serialisation/deserialisation, jedis record fetching/creation/existence checking.

- each endpoint class file follows a simple format: a static inner class is created for each resource (which represents a json document to be either serialised or deserialised using gson) and any methods returning jax.rs responses for the actual http requests related to the endpoint.

- the only unrelated changes are to `pom.xml`, the jedisclient class and removal of (seemingly) unnecessary source files.

as an ending note, it would be best to leave issue-14 unclosed as this set of features cannot be completely finished until other parts of the codebase are attended to (notably, the jedisclient and the rosafactory), though, this is a substantial starting point for the application endpoints.
I'm not fully understanding what the REST API is going to look like at this point. Would it be possible to get a very brief description as a comment on this PR? Just endpoints and maybe an outline of how they're expected to be called should be enough.