Close #140

1.  Create file `_includes/links.md` with definitions of all links.
2.  Replace links at the bottom of Jekyll'd `.md` files with inclusion of that file.
3.  Modify `bin/lesson_check.py` to load and check definitions in this file.

This eliminates most redundancy in link definitions, though
`CONTRIBUTING.md` and `README.md` still contain their own links, since
they are not Jekyll'd.  Note that we *cannot* put the links into
`_layouts/*.html` (or even `_layouts/something.md`) because of the
order in which Jekyll expands things - we have to explicitly include
it in each page.

1.  Remove copyright information about code of conduct (which isn't in this repo).
2.  Change ownership of trademark to NumFOCUS.
3.  Use uniform link syntax.

* Add `.nojekyll` to stop GitHub trying to compile.
* Get rid of Jekyll `_config.yml`.
* Create placeholder `css` and `img` directories.
* Create `pages` directory with source for web pages.
* Move all Markdown files into `pages`.
* Move `tools` into `pages` (because that's where people will mostly work).
* Move `_includes` and `_layouts` into `pages` (because that's where we'll compile).

Titles from the v4 release notes [1]:

* A more global license
* Rights outside the scope of copyright
* Common-sense attribution
* Enabling more anonymity, when desired
* 30-day window to correct license violations
* Increased readability
* Clarity about adaptations

[1]: https://creativecommons.org/version4

This is up for discussion, but at the moment is the
minimal set of files needed to be a Software Carpentry lesson.