Windows: Fix tests & building the mkdocs documentation on Windows

This pull request includes everything in #96.

Notable changes beyond #96:
* Include `ez_setup.py` for easier installation on systems without `setuptools` (such as AppVeyor CI), [as recommended by the `setuptools` docs](https://pythonhosted.org/setuptools/setuptools.html#using-setuptools-without-bundling-it)
* Changed one test to use `tempfile.mkdtemp()` instead of `tempfile.NamedTemporaryFile()` because Windows doesn't like to read open files
* Changed nav.FileContext.make_absolute() to use posixpath instead of os.path because it's only used to compare a filename against mkdocs.yml paths

This weekend I learned it's pretty easy to set up Windows-based CI for this:

1. Go to http://www.appveyor.com/ and click `SIGN IN` in the upper-right corner
2. Connect to GitHub
3. Make a new build, select the `mkdocs` repo
4. [Optional] In Settings &rarr; General, build all branches.
5. In Settings &rarr; Build, select `SCRIPT` and `CMD`, then enter `python setup.py install` and `c:\python27\scripts\mkdocs build`
6. In Settings &rarr; Test, select `SCRIPT` and `CMD`, then enter `python setup.py test`
7. In Settings &rarr; Artifacts, add `dist/*.egg` and the `site` folder (because why not).
8. In Settings &rarr; Badges, copy the Markdown snippet into README.md and tweak as desired.

...Looks like [steps 4- can also be set up with a YAML file](http://www.appveyor.com/docs/appveyor-yml).  Let me know if you'd like me to write/test/push one for you.

I hope I've done my homework well enough.  Please let me know if you still have any reservations about accepting this pull request.  I'd really like to start using mkdocs at work.
Ok, I fixed Virtualbox the other day, so here's what happens.

### Steps:

1. Git clone to ~/dev
2. Apply the changes as described above, including renaming mkdocs/mkdocs to mkdocs/mkdocs.py
3. Make & activate a virtualenv
4. Run `python setup.py install`
5. Run `mkdocs`

### Output:

```
(env)ed@ed-vm-u:~/dev/mkdocs$ mkdocs
Traceback (most recent call last):
  File "/home/ed/dev/mkdocs/env/bin/mkdocs", line 9, in <module>
    load_entry_point('mkdocs==0.9', 'console_scripts', 'mkdocs')()
  File "/home/ed/dev/mkdocs/env/local/lib/python2.7/site-packages/pkg_resources.py", line 356, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/home/ed/dev/mkdocs/env/local/lib/python2.7/site-packages/pkg_resources.py", line 2439, in load_entry_point
    return ep.load()
  File "/home/ed/dev/mkdocs/env/local/lib/python2.7/site-packages/pkg_resources.py", line 2155, in load
    ['__name__'])
  File "/home/ed/dev/mkdocs/env/local/lib/python2.7/site-packages/mkdocs-0.9-py2.7.egg/mkdocs/mkdocs.py", line 5, in <module>
    from mkdocs.build import build
ImportError: No module named build
```

Maybe there's some nuance about setting up Python packages I've missed that lets you type `from foo.bar import bar` inside `foo.baz`, but otherwise the fix appears to be relative imports everywhere within the `foo` package.