fix $thing parameter in deprecation helper

See https://github.com/dokuwiki/dokuwiki/commit/615810c59cd1bbc7a6f950fa667bd0c75f92d99a#r161070574

replace E_USER_ERROR triggers with RuntimeExceptions

The use of trigger_error with a E_USER_ERROR is deprecated in PHP 8.4

do not call get_class() without a parameter

This has been deprecated in PHP 8.3

code style: line breaks

coding style: control flow whitespaces

address issues mention in PR#4045

codestyle adjustments: function declaration braces/spaces

Apply rector renames

apply PSR-12 constant visibility rule

PSR-12 says constants need their visibility declared from PHP 7.1
onwards

Apply rector fixes to inc/Extension and inc/Debug

fix codestyle

another go at #3717

c0ece86a0ac0cfab0856b056fb3ce8e726855542 was wrong too, because most
deprecation logs drop the callee

Another fix for #3717

The deprecation mechanism did actually log the wrong file (callee
instead of caller). This was fixed and the message adjusted again.

A guardian for very short backtraces and l

Another fix for #3717

The deprecation mechanism did actually log the wrong file (callee
instead of caller). This was fixed and the message adjusted again.

A guardian for very short backtraces and large offsets was added

show more ...

log deprecation messages independent from allowdebug

Only the logging configuration should influnece if deprecation messages
are to be logged. By default they should be logged.

Fixes caller position when logging deprecated data

The backtrace lists the caller position for the called method. The code
assumed it to be the position of the methof itself.

better deprecation messages for self required plugin base files

central logging mechanism

This introduces a logger mechanism and a new data/log directory. This is
a first proof of concept. It's built on top of the new global error
handling mechanism

Things to d

central logging mechanism

This introduces a logger mechanism and a new data/log directory. This is
a first proof of concept. It's built on top of the new global error
handling mechanism

Things to discuss:

* should we adopt PSR-3 somehow? if yes, how and should plugins be able
to drop-in other psr3 loggers?
* how to configure which facilities shall be logged?
* should we implement a log deletion feature?
* is the log format sensible?
* should we implement a log viewer admin plugin?
* should logging trigger events (it should maybe replace the
deprecation event)

show more ...