Bring in history for the setup/ directory and merge swc-nano-installer.py into its swc-windows-installer.py predecesor

Get a feel for how master's `setup/` directory evolved in the boot-camps repository.

    $ git log --graph --topo-order --oneline --decorate master -- setup/

Pull swcarpentry/boot-camps#31 out into its own branch:

    $ git log --oneline --follow setup/get-my-ip.py
    $ git checkout --orphan get-my-ip
    $ git rm -rf .
    $ for HASH in $(git log --reverse --pretty=format:%H master -- setup/get-my-ip.py); do git cherry-pick "${HASH}"; done

Pull swcarpentry/boot-camps#47 out into its own branch:

    $ git log --oneline --follow setup/swc-windows-installer.py
    $ git checkout --orphan windows-installer
    $ git rm -rf .
    $ for HASH in $(git log --reverse --pretty=format:%H master -- setup/swc-windows-installer.py); do git cherry-pick "${HASH}"; done

Pull swcarpentry/boot-camps#12 out into its own branch.  This is
easier because I initially developed it as a stand-alone branch
so I don't need to detach the root from the abandoned boot-camps
stuff:

    $ git checkout -b installation-test 901e025
    $ git cherry-pick a7f166b

Create a new branch to land these with:

    $ git checkout -b bc-setup bc/gh-pages

See what's been going on in the setup directory:

    $ git log --oneline --decorate -- setup/
    64f4940 (bc/pr/64) removed stray non-printing unicode characters
    f461fbf (bc/pr/35) Remove testing line
    af1ec77 Append exports to end of .bash_profile instead of overwriting
    ce6ca59 Switch from using .bashrc to .bash_profile nano path and editor export
    f4e0254 Add a Nano installer for Windows
    01d6419 (bc/pr/16) Import installation test scripts from boot-camps repo.

Take a look at what swcarpentry/bc#16 pulled in:

    $ git ls-tree -r bc/pr/16 setup/
    100644 blob e7c519386733b9c96861853356dae1918f943b64    setup/bin/README.md
    100755 blob 6b93ca13a65f815220771132845e228ce67835d3    setup/bin/get-my-ip.py
    100755 blob be027f937fe220bfc45788c123319f48940e3766    setup/bin/swc-installation-test-1.py
    100755 blob 7f55b337c40a909f3b4c480a79912d1d9ec5837b    setup/bin/swc-installation-test-2.py
    100755 blob c0bde19f800100e1ced14e98f706dbcb14c551a8    setup/bin/swc-windows-installer.py

How does that compare with my installation-test branch?

    $ git ls-tree -r installation-test
    100644 blob e7c519386733b9c96861853356dae1918f943b64    setup/README.md
    100755 blob be027f937fe220bfc45788c123319f48940e3766    setup/swc-installation-test-1.py
    100755 blob 7f55b337c40a909f3b4c480a79912d1d9ec5837b    setup/swc-installation-test-2.py

Looks like we have a perfect match for each of the files I have,
but the get-my-ip.py and swc-windows-installer are also in
bc/pr/16.  Do *those* match my branches?

    $ git ls-tree -r get-my-ip
    100755 blob 6b93ca13a65f815220771132845e228ce67835d3    setup/get-my-ip.py
    $ git ls-tree -r windows-installer
    100755 blob c0bde19f800100e1ced14e98f706dbcb14c551a8    setup/swc-windows-installer.py

Also perfect matches.  What about subsequent bc development?  The
substantive development was for bc/pr/35 which adds
swc-nano-installer.py, a close relative of swc-windows-installer.py.
I'll consolidate these in a moment.

I've left off the bc/pr/64 changes to the README.  From
@wltrimbl's [comments][1]:

> It looks like most of these were present in the old boot-camps
> repository. Because of their positions, I presume these were
> unintended side effects of a format conversion or a
> cut-and-paste gone bad. The unicode characters that are
> intentional--in strings and in names--I have not disturbed. But
> these are symbols that do not seem to be purposeful.

My ellipses were purposeful ;).  I'm happy to add `-*- coding: utf-8
-*-` magic comment to the file, but Markdown doesn't have a comment
character…

Alright, time to merge my stuff in.  Since rebasing is not allowed,
I'll merge each of my branches, then remove the historyless content
they replace, and squash the removal into the merge with an
explanatory comment.

    $ git merge --log get-my-ip
		$ git rm setup/bin/get-my-ip.py
    $ git commit -a --amend
    $ git merge --log windows-installer
    $ git rm setup/bin/swc-windows-installer.py
    $ git commit -a --amend
    $ git merge --log installation-test
    $ git rm setup/bin/{README.md,swc-installation*}
    $ git commit -a --amend
    $ emacs setup/swc-windows-installer.py
    $ …

Someone with Microsoft Windows access should test my
`swc-windows-installer.py` changes before we merge this PR.
Also, if the IPython and nose entry points are no longer required,
it would be nice to remove their creation code with an explanatory
commit message.

[1]: https://github.com/swcarpentry/bc/pull/64#issuecomment-26168019