CI: use versioneer to have PEP440 versions
- use versioneer, for PEP440 version strings, closes #9518 
- use binstar build
- OSX stack testing, closes #7127

This removes all of the original manual-ish logic to create/manage the versioning in `setup.py`, and replaces with `versioneer.py` (bundled inline) to handle correct versioning for release, development, and conda builds.

This actually was tricky simply because of the way the tags are setup, they are like: `v0.16.2` which is pretty non-standard, e.g. most would simply have `0.16.0`. This messes with comparision using `LooseVersion` (of course you _can_ replace this tag as versioneer does, its called the `tag_prefix`, but his makes other things require a slightly different method).

So bottom line we get PEP compliant versions like this:

```
In [1]: pd.__version__
Out[1]: '0.16.2+10.gc01927b'
```

IOW, 10 commits past the last tag and the git hash.

Now also able to build on `anaconda.org` for all platforms (`linux-32,linux-64,OSX,win-32,win-64`). This part is not 100% done, but quite close. The intention is to have testing and artifact building (well at least for say 2.7/3.4) for linux,osx,win that can be directly `conda install pandas -c pandas` to get the dev version.
