This reverts commit 524d28fd.

These interfere with JSON-LD activitypub requests because
apparently the '; profile="..."' part is matched by that humongous
rule 920600 regexp and ModSecurity thinks it's a charset.

Attempts to fix the content negotiation caching issue #134.

Apparently gotosocial uses it for profile discovery.

Remove caching from pages ending with a / which MAY (or may not, more
likely) help in resolving issue #134.

Update the list of mobile user agents.

The cache/.htaccess mechanism should actually be moved into
the apache2 config, instead of the current hackish solution...

Needed to find wp-cli, a dependency of noblogs-cli.

The theory is that nowadays most themes are responsive, so there's
no need for custom "mobile detection" logic anymore. Try to validate
the theory starting with Android devices.

The WP-Supercache Apache caching will anyway cover NGINX
requests for 300s.

In case it's a tmpfs.

Specifically fix the cached files path.

Drops the 'must-revalidate' bit, which prevents serving stale pages,
and sets a longer max-age to match the edge NGINX caching ttl.

Attempts to fix issue #114.

Avoids an extra SQL lookup on every request (a drop in the
ocean, but still).