Let documents {attach} static files. Fixes #1019.

Until now, making static files end up in the same output directory as an article that links to them has been difficult, especially when the article's output path is generated based on metadata. This changeset introduces the `{attach}` link syntax, which works like the `{filename}` syntax, but also overrides the static file's output path with the directory of the linking document.

It also clarifies and expands the documentation on linking to internal content.
Example is fine. It's not my concern. Removing one of the hierarchies is confusing and would potentially cause trouble. e.g.:

What if someone has `/downloads/example.zip` and `/downloads/tutorials/example.zip` and use `{attach}` for both?