End-to-end test recipe enabling going into remote settings

[peterbe]

We currently, in CircleCI, start the django web server and run the contract-tests on it with pytest. Those tests currently don't test the full cycle of enabling a recipe and making sure it ends up in Remote Settings.

For this to all work we need to do two things:

1. Start remote settings and autograph in ci/docker-compose.yml
2. Extend the contract-tests so it enables a recipe and enables them and then it should be able to see the recipe in remote settings's main bucket/collection.

NOTE! The contract-tests are currently used in two places:

1. Our CircleCI
2. System tests run as part of the deployment.

Because of that, we can't de destructive things in these contract tests because, when run as a system test it would potentially hit real databases with real (bad) changes.