Abstract out reliance on DRF response structure

[baylee]

Currently we are assuming that list responses follow a Django REST Framework list response structure, e.g.:

{
    "count": 26, 
    "next": null, 
    "previous": null, 
    "results": [
        {},
        {}
    ]
}

We are automatically pulling out results as the objects of interest. This will break for any API that just returns results as a simple list, or with a different key.

Some options to resolve this could be:

• specifying a keyPath in the schema (e.g., for DRF the keyPath would be results)
• do the above and also save the meta data
• something else?

[baylee]

Ah, I see we kept the keyPath logic in the templates. @rmutter I'm happy to add this back to the parser and update the templates if you think it's the way to go.

[rmutter]

@baylee I don't know if there would preferably be a global default as well as a way to configure it per endpoint. Globally may be the more valuable feature to implement first.