REST extend all functions to suppose HATEOAS based HTML interface

[adamfowleruk]

Each REST endpoint should be capable of rendering a HTML output to a browser. This should be kept very, very basic. When invoked from a browser (with an Accept-Types including text/html as a preference), the REST endpoints should show HTML output.

This output must include links to actions that this user can attempt. E.g. a listing of processmodels should show links to downloading the model, deleting the model, publishing the model, and uploading a new model. They may also include extended links for, for example, showing all process instances currently running of this model.

This will provide a human readable interactive way to work with the rest endpoints and discover valid ways to invoke and use them. It also provides a very basic UI for demo-ing MarkLogic Workflow capabilities. It will also be useful for testing or administration.