[TASK] Formatters must use date formats from TYPO3_CONF_VARS

The Date formatter uses the format from
$GLOBALS['TYPO3_CONF_VARS']['SYS']['ddmmyy']

The Datetime formatter uses the format from
$GLOBALS['TYPO3_CONF_VARS']['SYS']['ddmmyy'] and
$GLOBALS['TYPO3_CONF_VARS']['SYS']['hhmm']

Resolves: #57520
Change-Id: Id17cd03b48ae7f22d8486b626f21152e1f33a729
[BUGFIX] datetime formatter fails to load

When using "datetime" formatter, vidi ends up in a fatal error.
It seems that class_exists('datetime') always return TRUE,
because of native PHP \DateTime class.

The regression was introduced by #57489

Resolves: #57558
Change-Id: I2d86fee188dd88bbb638a272b2f161066fc34f97
[BUGFIX] Malformed special characters with PHP 5.3

Grid/RowViewHelper uses PHP function htmlentities() without an
encoding argument.
The default encoding of htmlentities() has changed from ISO-8815-1
in PHP 5.3 to UTF-8 in PHP 5.4.
Since TYPO3 uses UTF-8 as default character set for data handling,
we force UTF-8 in any htmlentites() call to gain compatibility
with PHP 5.3.

Resolves: #57538
Change-Id: I12b1195b5a2b0d0c6bc2a7249b70af67db99de5d
Merge "[BUGFIX] Malformed special characters with PHP 5.3"
[FEATURE] Improve exception message if Ajax went wrong

The change-set prevent the UI to freeze in case
the Ajax requests went wrong. Previously, a basic
javascript alert was raised up.

Change-Id: I75cbdc8a057cccee43756f580df79eb090923926
Releases: 0.3.0
Resolves: #57643
[BUGFIX] Encode link URL in RelationCountRenderer

The Grid/RelationCountRenderer renders a link to the
related datatype. The link URL contains special characters,
which need to be encoded.

Resolves: #57570
Change-Id: I5294cdd093af0fae47c9489e1f44f3d83fe5de6b
Merge "[TASK] Formatters must use date formats from TYPO3_CONF_VARS"
[TASK] Streamline error message when Ajax request goes wrong

Change-Id: I7d3d5d2517e551f1b2b11839cda35435965c9b7b
[RELEASE] 0.3.0

Change-Id: Ib059dca493e6ff9bed5fec69e0b8060d2d9008d1
Releases: 0.3.0
Resolves: #57784