Fix .htaccess files for Apache 2.4 (and 2.2)

Change `const` use to `var` for Safari 9 (on iOS)

Safari 9 in iOS does not support the use of `const` in strict mode. Unfortunately, some of us are stuck with Safari 9 due to not being able to upgrade.

I am a big fan of progressive enhancement, but because all javascript code is packed together and sent off to the client, this small incompatibility breaks all javascript for safari 9 browsers. Switching these two keywords makes everything work again.

There are no other uses of `const` in the codebase as far as I can find. This change has little to no impact on anything else, but slighlty extends the range of supported browsers.

Refer to module by suitable file name (mod_*.c).
Test for mod_authz_core.c (instead of mod_authz_host.c) to properly
detect Apache 2.4 and avoid false positive for Apache 2.2.

 (Draft) Fix exception when actually viewing a draft of a page

Not sure why this didn't show up sooner 

Better draft handling

Add unittest for deleteUsers remote API call

Remote API calls should have some unittest as this test would have caught
the bug that was introduced in 96d46bf4
and fixed in ebf17449

The parameters passed to triggerUserMod() were wrong.

Translation update (no)

Plugins may want to add further fields to be present when saving drafts.
Plugins may want to execute some js functionality that should be timed to
the saved draft/refreshed lock.

If a plugin does another init() to attach the dw_locktimer to its own editor,
then the default callback would be added a second time, causing unexpected
and undesired behavior.

This includes the changes from the following commits:
6ef45cc1
6ca947f3
0fff419c
87bed8b6

This change is useful for plugins that may want to implement their own toolbar (and thus hide the
default toolbar), but still would like to let the locktimer set the draft status.

Translation update (fy)

introduce INFO_DEPRECATION_LOG event

now the method is aborting early again unless the data is actually used

Sometimes, preparing the data for an event is expensive and only needed
if the event is actually handled. This allows for a quick check before
actually preparing and triggering the event.

This adds an event to dbg_deprecated(). This allows plugins to handle
deprecation warnings. One example would be @cosmocode/dokuwiki-plugin-sentry

One thing I don't like, but don't know how to avaoid is that this
function used to abort super early when $conf['allowdebug'] wasn't set.

However for the sentry plugin you probably would want logs, but still do
not show any debugging to end users (which allow debug would do).

So now the backtrace is always built, the event triggered and then
everything is sent to dbglog() which may simply throw everything away.

Suggestions on how to improve this welcome.

Add call to delete Users to the remote API

These shouldn't be there anymore since the plugins have been deleted

Translation update (de)

PHP brekas URLs by moving old releases into an archive folder. Since we
cannot be bothered to update these tests everyday, versions have now be
adjusted to be slightly older to always go to the archive download.

use more general phpunit versions

Appveyor seems to have problems with redirects by php sometimes

Fix for Issue#1250 Footnotes break metadata abstract saving

New event for trimming recent changes and refactor lib/exe/indexer.php

Translation update (cs)

Translation update (it)