Othewise weird side effects may happen when a parent constructor
overwrites them again.

Even for our own namespace, file existance should be checked before
attempting to load it. Otherwise class_exist() check will throw errors.

I want to make this function use the new Menu Items, these tests should
ensure I don't break functionality.

* master:
  make Doku_Form members public again. fixes #1982
  translation update
  Fix minor typo in the distributed user configuration
  Adjusted pattern for matching media links to properly handle a single '}' in the link text. Fixes #1587.
  Added green and red text color styles for geshi. Improves look of highlighted code for language diff. Fixes #900.

Various plugins access the form members directly currently.

getLink() now no longer escapes ampersands - this is task of the code
producing the HTML. When using asHtmlLink(), buildAttributes() will take
care of the escaping for you.

Adjusted pattern for matching media links to properly handle a single '}' in the link text. Fixes #1587.

Added green and red text color styles for geshi. Improves look of highlighted code for language diff. Fixes #900.

* master: (80 commits)
  use composer based library for feed creator #1970
  fixed typo in methodname
  updated GeSHi to 1.0.9.0
  refomatted mail tests to use data provider
  fix error in config manager caused by changes visibility
  Continue if there are no attributes
  avoid dependency tests being marked as risky
  replaced some more each calls
  remove deprecated each() call
  test constructors need to call parent constructor
  use dataprovider in password tests
  removed deprecated blowfish class
  replace some var keywords
  translation update
  PassHash.class.php: in case of brcrypt, use the most recent variant $2y$
  translation update
  Fix Typo in remote API (#1938)
  translation update
  translation update
  translation update
  ...

This basically reimplements tpl_action_dropdown but makes use of the
other menus (by setting the context to mobile) and thus still triggers
the appropriate events. This makes #1598 obsolete.

tpl_action_dropdown (and the other tpl_action* methods) still need to be
replaced to make use of the new Menu system.

this adds an option to print the menu without icons (as we do in the
dokuwiki template) but icons were added nontheless

also adjusts styles and adds images

all menu items should have a default SVG. Template authors then can
decide if they want to use them or not.

These are only the page tool SVGs. More need to be added.

This is an attempt to:

* get rid of the super long, complex functions in in/template.php
* make it easy for plugin authors to add their own items to any
  of our menus, regardless of the used template
* continue the progress to make use of SVG in the menues

This takes a similar approach as my actionrefactor branch. Originially
I thought both refactorings could be done in one, merging the
functionality of DokuWiki actions and the menu items. However I couldn't
make it work. So instead we have two separate but similar things.
Maybe they can converge later on.

The internal lang and localized variables of a plugin are no longer
accessible from the outside. This adds a proper setter and also fixes
the type hinting in the config plugin.

If an entry in the loop at `_tpl_metaheaders_action` has no content, skip this entry.

There are still some left in the DifferenceEngine code

this fixes another problem with our tests and phpunit 6.1

This fixes a problem with those tests in the most recent version of
phpunit. I thought it was caused by the use of the deprecated var
keyword, but some other weirdness was going on. This way it's more
proper anyway.

This should fix some tests on PHP 7.1. The work is far from done, we
still have a lot of variables without proper accessibility defined.

This change breaks compatibility with php 5.3.7, but a standing
requirement for at least php 5.6 is declared in composer.json.

If the php documentation is to be believed, this change increases
security against pass-the-hash type attacks. (I do not have the knowledge
to assess the security differences between $2a$ and $2y$).

As a Sidenote: htpasswd shipped with apache2 2.4.10 (and probably,
other versions), when used with the -B (=bcrypt) option, produces hashes
marked with $2y$.

Nonewithstanding the actual support or non-support of $2a$ by the
apache2 'AuthUserFile' directive, the apache 2.4 documentation only
asserts support for the $2y$ bcrypt variant.
Therefore, this commit would make it possible for dokuwiki and apache2
basic authentication to share the same password file, in the case when
bcrypt is used.