Communication with matching

[reginafcompton]

Overview

This PR modifies mci user handling to accommodate the mci-matching-service.

• Removes the matching algorithm and replaces it with a request to the matching_service_uri (e.g., http://mcimatchingservice_mci_1:8000/compute-match)
• Adds a property as_dict to the Individual model, so POST'd user data can be easily jsonified
• Adds a docker-compose-develop for ease of developing alongside matching service

Testing

Pull down this branch, and follow the instructions provided in the README of the matching service repo: https://github.com/brighthive/mci-matching-service#setting-up-for-local-development

[gregmundy]

@reginafcompton code looks good, go ahead and resolve the conflicts and merge the branch to master and I'll stand it up in a local testing environment.

[reginafcompton]

@gregmundy - great. I'd recommend that, first, we merge and deploy https://github.com/brighthive/master-client-index/pull/4: it puts the database into a standalone package (a preliminary step in getting the mci-matching-service in proper shape).

Do you have a staging server set-up? If so, I'd be happy to deploy the MCI changes myself – or we could pair?