Set explicit caching everywhere.

This explicity sets the caching behavior for all goodies. Goodies which
did not have caching behavior set in their package have had it added.
Similarly for the tests.

This resulted in a number of changes for caching behavior, mostly
moving towards more frequent caching.

I identified three cases where goodies should not be cached. They are when
the result depends upon:

- some random element,
- the time of day or year (as with relative dates), or
- the location of the requesting user

In all other cases, I presumed that the goodies were sufficiently
deterministic in their output to warrant caching.
Ah I see, "last year's zodiac" won't always have the same response. In that case, we're actually able to modify the caching in the return statement. So we can cache by default, and for the cases where we don't need to the return would look like so:

`return answer => foo, html => <p>foo</p>, { is_cached => 0 }`