Aliases that have no directory nesting sneakily avoid the code path that ensures the directories exist

Closes #485

Local CSV/TOML/JSON loading Tera function

Close #446
Close #260
Close #478
Close #284
Close #480

Switch to an `Option<usize>` for the serialized value of `rss_items`.
This lets us just set a blank value in the configuration and thereby
include *all* items.

This is a backwards-compatible change; it does not affect the behavior
of existing configurations.

Fixes #468. Closes #471.

Fix #122

Fix #205

This allow to use base_url in robots.txt, to reference a sitemap for
example.

Closes #443

Not only is this tidier, but it avoids making these iterators
Rayon-specific.

This offers a big performance bump for large sites:

  small-kb (100 pages)
    before: 530ms
     after: 500ms

  medium-kb (1000 pages)
    before: 2.9s
     after: 1.5s

  huge-kb (10,000 pages)
    before: 150s
     after:   9.1s

Closes #403

Fix #412

This reverts commit c7156a84f0.

Replace `populate_next_and_previous_page` with `populate_siblings`

This commit removes the option to sort by order and also removes
`page.next` and `page.previous` variables.  Instead, pages can be sorted
by two methods `date` and `weight`.  The Tera `reverse` filter will
reverse either of those sorts, so the old `order` behavior can be
achieved by using the `reverse` filter with `weight`.

In place of the `previous`/`next` variables, this commit adds the
`page.earlier`/`page.later` variables (which are set when the page is
sorted by date) and the `page.heavier`/`page.lighter` variables (which
are set when the page is sorted by weight).  These variables have the
advantage of not having confusing semantics when the `reverse` filter is
used.

Since we are using a builtin template, we can be assured to have the
target file in place. Middleware renamed since it is bound directly to
the concept of handling 404s.