)

Use TYPO3\CMS\Frontend\Authentication\FrontendBackendUserAuthentication
instead, the class has been moved from ext:backend to ext:frontend in
TYPO3 v13, the old name has been established as alias and is
removed with TYPO3 v14.

…collate)

This reverts commit cd23e9f,
which was a experimental try to mitigate an issue with scheduled
execution breaking external fork pull-requests. It's not needed
and removed again.

With the introduction of non-main branch scheduled workflow
execution a adjusted checkout part in the `ci.yml` workflow
file has been added to allow to define which branch should
be checked out.

That breaks pipeline execution for pull-requests opened from
repository forks.

This change replaces the old detection with a more simplified
implementation, only setting the custom ref in case of github
workflow_dispatch event execution using `''` as fallback which
allows custom branch selection for workflow dispatching while
keeping default repostiory and branch checkout intact.

Releases: main, 8, 7

> composer req --dev friendsofphp/php-cs-fixer:^3.65.0

Releases: main, 8, 7

> composer req --dev phpstan/phpstan:^2.0.2 phpstan/phpstan-phpunit:^2.0.1
> Build/Scripts/runTests.sh -s phpstanGenerateBaseline -p 8.2

Releases: main, 8

When comparing with a csv fixture that contains a table
with no rows, which is a legit case, no assertion is
raised. This makes phpunit emit a risky test: "This test
did not perform any assertions". The patch adds an
assertion in this case as well.

Note phpunit nowadays has attribute #[DoesNotPerformAssertions]
to mark tests that do not assert anything. This can be used
for tests that for instance just call a subject method to verify
no exception is raised. It is good to follow this path, the
patch removes "beStrictAboutTestsThatDoNotTestAnything=false"
from the example phpunit xml files, which makes this setting
implicitly true.

Releases: main
Resolves: #647