No-clone/pip-only install process for end-users (as opposed to developers)

[rallen10]

To unify the install process, need to make the entire kspdg package pip-installable without need for cloning the repo. This way there is less variability between users as to whether they are cloning and modifying kspdg, versus pip installing it as a dependency within some other project/conda environment

Steps to complete:

• Make the install_julia_deps.py script a command-line entry point
• Make the unit tests command-line entry points
• Add ksp mission files to package data and a entry point script for copying them to end-user's KSP install directory
• Rename the kspdg conda environment to kspdg-dev to distinguish it as a developer environment, as opposed to end-user
• Update README to give different install instructions for end-user versus developer, where end-users have a no-clone, pip-only workflow

[rallen10]

Additional Steps:

• make evaluation/ a package entity and create an command-line entry point for its use
• Update README with new evaluation process