Installing package via pip does not install the json configurations

[llvtt]

This is intentional. Installing the JSON configurations is problematic:

• It's unclear where configurations should be installed.
• It complicates setup, since we'll have to set MONGO_ORCHESTRATION_HOME to point at the configurations. This could be accomplished on linux-like systems by modifying .profile or something similar; not sure what would need to happen on Windows.
• Some of the configuration files need to be used with mo, which is written in Bash. This won't make any sense on Windows.
• If we included configurations as part of the mongo_orchestration package, then then would end up in somewhere within a site-packages directory, which would be difficult to find and later use with curl or any other tool.
• It's unnecessary. The user can clone the repository and have control over where the configurations are going and setup their environment as they see fit.

[TylerBrock]

I think its clear where they should be installed and the code would not be platform dependent if done correctly.

The configurations should be installed where the package is so they can be upgraded with the package. Then in python you can do the following

import site
site = site.getsitepackages()
// get config relative to site[0]

[TylerBrock]

Additionally, I think installing the configurations is a must have for this project. The entire point of this project is testing across drivers via standardized configurations. If we cannot do that via the package alone it is major problem.

[llvtt]

configurations installed by pip in 89fafbdb7b29cdfc5be128bac0f8ea739fa6de0d