fix(controller): properly serialize JSONField objects

JSONField is a finnicky thing. When serializing the object in the API,
it will just dump the object as a string. This ends in an invalid JSON
response. In the case of the Config object:

    {"owner": "bacongobbler", "app": "go", "values": "{\"HELLO\": \"world\"}", "memory": "{}", "cpu": "{}", "tags": "{}", ...}

This fix changes the JSON output to the following:

    {"owner": "bacongobbler", "app": "go", "values": {"HELLO": "world"}, "memory": {}, "cpu": {}, "tags": {}}

This is completely backwards compatible with previous requests. The
JSONSerializer will accept both strings and JSON objects in the request.
fix(controller): retrieve logs via GET request
fix(builder): properly parse config vars

Previously, the entire export from `jq` was considered one string, so
when we printed the output it would be like "-e HELLO=foo GOODBYE=bar".
This fixes it to "-e HELLO=foo -e GOODBYE=bar".

I also removed the for loop in favour of a list as bash invokes a
subshell in for loops, losing any data you set (such as BUILD_OPTS).
style(builder): fix typo
fix(controller): set default config owner to request.user
fix(controller): don't clone run containers on deploy
Merge pull request #2145 from mboersma/ignore-run-deploy

fix(controller): don't clone run containers on deploy
Merge pull request #2116 from bacongobbler/apiv1

API v1 fixes
chore(controller): remove unused django-allauth app
fix(auth): use djangorestframework login/logout views