Beef up Kubernetes introspection on API tests

[Cryptophobia]

From @helgi on September 15, 2016 19:7

Right now we generally just test that an AppSetting was created, updated and deleted... We are mostly exercising Django and DRF at that point, making sure some nuances are taken care of in the way we wrote a model or serializers.

The proposal here is to change tests to verify that Services are being updated, pods are created for autoscale, etc etc - Scheduler tests already takes care of a lot of that but more in-depth could be good

This is just taking AppSettings as an example and would apply to any model we have. Would prevent problems we saw with IP whitelisting, maintenance mode, routing and a few other things over the course of the project

Copied from original issue: deis/controller#1065