Consider keeping code search binaries in the project #7
Description
It's pretty easy to create Go binaries for Windows, OSX, Linux, and FreeBSD; so maybe we can eliminate an installation step for the user by just keeping copies of the binaries in the project.
CodeSearch hasn't seen a lot of change, so there doesn't appear to be a lot of re-syncing that needs to be done. It also means that there's a version of the csearch and cindex app that have been verified to work with the plugin, which could mean less bugs if there was a big change into those apps.
One question that will need to be answered is if the binaries should be stored within git and served via Package Control with the .no-sublime-package file or if I should just host a .sublime-package for the plugin code an an executable package for the bins.