Add missing "App" node to example in Changelog
of notification actions.

Resolves: #104903
Releases: main, 12.4, 11.5
Change-Id: Icc88a55c731c7f5b517740673c24acd21b83fa12
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85957


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>

The package `mime-db` received some updates since its introduction,
hence it is now updated to its latest version.

Executed commands:

    cd Build
    npm install --save-dev mime-db@^1.53.0
    ./Scripts/generateMimeTypes.php

Resolves: #104743
Releases: main, 12.4, 11.5
Change-Id: I756eed3e8d1a6b02f7b2f855dc63623a0c97245e
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85980


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>

This fixes the rendering warnings due to duplicate anchors
and provides more structure in general. Also utilize
API docs referencing for FQCNs.

Resolves: #104712
Releases: main, 12.4, 11.5
Change-Id: I4e088dacec80a44d7c6e24ebb07582cbe84f72a2
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85753


Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Backport of #104694 for TYPO3 11.5 with PHP 7.4 introduced an example
that was not lintable.

This patch addresses that and removes PHP 8 language syntax features
from the example code.

Resolves: #104826
Related: #104694
Releases: 11.5
Change-Id: I390a05e6ffad948a32cd1d12134f3e7c0fdc7049
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85895


Tested-by: core-ci <typo3@b13.com>
Tested-by: Chris Müller <typo3@brotkrueml.dev>
Reviewed-by: Chris Müller <typo3@brotkrueml.dev>
Tested-by: Torben Hansen <derhansen@gmail.com>
Reviewed-by: Torben Hansen <derhansen@gmail.com>
Reviewed-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: Garvin Hicking <gh@faktor-e.de>

This patch shows an example for the frontend login
how to get a redirect when an unauthorized visitor
tries to access a restricted page.

In this case, a 403 ErrorHandler can perform a
redirect with special parameters, that a properly
configured felogin plugin can utilize to
redirect back to.

Resolves: #104694
Related: #101252
Releases: main, 12.4, 11.5
Change-Id: Ia2c6723621304b8b3de366590c1be905572b00d1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85817


Reviewed-by: Garvin Hicking <gh@faktor-e.de>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
(cherry picked from commit 59b7da06)
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85877

The module "EditModule" was removed with #87498, but the
documentation reference remained. Instead of using this module
as an example, instead "CacheModule" is referenced, since it
addresses similar demonstration purposes.

Backports are needed for proper documentation rendering.

Resolves: #104802
Related: #87498
Releases: main, 12.4, 11.5
Change-Id: Iab25eec9aec9765f1c71f439c00ca34975d7e8a1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85873


Tested-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Garvin Hicking <gh@faktor-e.de>

Resolves: #104749
Releases: main, 12.4, 11.5
Change-Id: I0285dbeb8cabd4dc338797b6b47d3312ca2b9bb3
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85762


Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

This change upgrades the version of the used
`typo3/core-testing-php84` image [1], which
uses PHP8.4 beta3 now along a new version of
composer (2.7.8).

[1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/bd98c246f5f8e5e91ee835212122998ffa5a1298

Resolves: #104748
Releases: main, 12.4, 11.5
Change-Id: I6555332a05e5809e30381c3a6b363a84c0150815
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85759


Reviewed-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Garvin Hicking <gh@faktor-e.de>

This sets the correct code-block caption definitions for the YAML
and PHP code blocks so they will be rendered correctly.

Resolves: #104716
Releases: main, 12.4, 11.5
Change-Id: Ic1ecc908c5e84f0c72180e4402296a78211263b3
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85756


Tested-by: Chris Müller <typo3@brotkrueml.dev>
Reviewed-by: Chris Müller <typo3@brotkrueml.dev>
Reviewed-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: Garvin Hicking <gh@faktor-e.de>

The FileClipboardCest waits for a button to become 'enabled' before
clicking it.

Disabled buttons use `class="disabled"` with CSS `pointer-events: none`.
This might not be handled properly by `$I->waitForElementClickable()`.

Resolves: #104702
Related: #104585
Releases: main, 12.4, 11.5
Change-Id: If0677eb445207612f43b624c2889d7ef6651ae71
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85737


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Stefan Bürk <stefan@buerk.tech>

A broken backport for #103298 introduced some
not properly resolved changes.

This patch removes the wrongly merged blocks and
further adjusts indentation and class schemes
for the 11.5 context.

Releases: 11.5
Resolves: #104671
Related: #103298
Change-Id: I9471144476424e2e72adca6b02a58e12d3503f6d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85697


Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: Sandra Erbel <erbel@analog.de>
Reviewed-by: Garvin Hicking <gh@faktor-e.de>
Reviewed-by: Sandra Erbel <erbel@analog.de>
Tested-by: Garvin Hicking <gh@faktor-e.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

Resolves: #104639
Releases: main, 12.4, 11.5
Change-Id: I74a0cd9e856283d26a382582cc5d6b8e99887cd4
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85699


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>

The change in #97498 introduced a specific handling for ENUM/SET
definitions in MariaDB systems. The check may be performed with a
NULL value instead of a string, which can result in a PHP type
mismatch error.

Due to other refactoring, the issue does not exist in main (v13),
but only affects v12 and v11.

Resolves: #104621
Related: #97498
Releases: 12.4, 11.5
Change-Id: Ia28aae519b1aebcabe9a5f5c620124dfd22edc6a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85468


Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

Change-Id: I923ac886427a99eb9a3d7d50799e7e1f4aba2fcd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85605


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>

Change-Id: I69b661793f76067cda23b460d1a1aac1bd0896bd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85604


Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

idn_to_ascii() must not be called with empty
string in PHP 8.4.

Resolves: #104587
Related: #104513
Releases: main, 12.4, 11.5
Change-Id: I649d157cca3dadbe237e20eb440b071a1885db71
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85581


Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Jasmina Ließmann <minapokhalo+typo3@gmail.com>
Tested-by: Jasmina Ließmann <minapokhalo+typo3@gmail.com>
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85583

Wait for the drop down to be ready
before clicking around on it.

Resolves: #104585
Releases: main, 12.4, 11.5
Change-Id: I9fa86d99b02c74bcc0f9efebce8fc4c2f8e54af5
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85579


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

Wait for the modal body iframe being there before
switching to it. This is mainly an issue in v11
where the modal takes more time server side and
webdriver is 'too quick' switching to it. We
still sanitize all branches.

Resolves: #104577
Releases: main, 12.4, 11.5
Change-Id: Ida09f1945daae3d0fb396f1e495e91ed5042454a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85565


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

If an invalid record in `sys_be_shortcuts` is stored like this:

```
INSERT INTO sys_be_shortcuts (userid,route,arguments)
     VALUES (1,'record_edit','[]');
```

then the backend cannot be accessed anymore due to PHP
errors due to unguarded array key access of the
"arguments" contents.

This patch guards the array key access to prevent such
a situation, so an invalid shortcut can be deleted from
the menu.

Database records like this might happen for migrated older
installations.

Resolves: #104496
Releases: main, 12.4, 11.5
Change-Id: I350e620eb403e53d1828cf5dedaab633ba00db55
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85464


Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

composer/composer as dev dependency got a
security release relevant for monorepo.
We should raise to it.

> composer req --dev composer/composer:^2.2.24

Resolves: #104556
Releases: main, 12.4, 11.5
Change-Id: Ib9b81a942456f1ac78445f27b4b0b198ff204e2d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85541


Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

Resolves: #104557
Releases: main, 12.4, 11.5
Change-Id: I1bea6d74fc444007c8787e0a642c86b35a7ccb90
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85538


Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>

Doctrine DBAL retrieves for MariaDB `ENUM()` and `SET()`
field default values quotes with single quotes, which
leads to an endless field change reporting recursion in
the database analyzer. The default value is now trimmed
to ensure a working field compare within the extending
`TYPO3\CMS\Core\Database\Schema\Comparator` class.

Note that TYPO3 v13 (main) may reveal the same issue but
is shadowed due to the general `ENUM()` and `SET()` type
field issue since Doctrine DBAL 4, reported in #104413.
That needs a change on its own for main only.

Resolves: #97498
Related: #104413
Releases: 12.4, 11.5
Change-Id: I51b79a7f63db43cca2724958b0355a496a49fd33
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85460


Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

SiteResolving will now correctly interpret a temporary ID of a new page (e.g., "NEW12345678ABCDEF") as an invalid ID and try to infer the site using `$result['effectivePid']`.

This makes it possible to access site configuration properties within the TCA also on pages that have yet to be created.

Resolves: #103573
Releases: main, 12.4, 11.5
Change-Id: I174e71e084e96b24ebe721ad0336a3dd1a8115d9
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85458


Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>

Resolves: #104513
Releases: main, 12.4, 11.5
Change-Id: I73d4d5eac80e3bd637fa2fabd7b1d1948daf357c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85430


Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

In the RestoreRegisterContentObject::render method a call
to array_pop is performed. The result is assigned to the
variable $frontendController->register which has type array.
However array_pop can return null, this patch add's a
null coalesce operator to ensure that correct type.

Resolves: #104495
Releases: main, 12.4, 11.5
Change-Id: I46efce10e4322ff3cd39b5a0eeafd1f768644e38
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85359


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>

PHP 8.4 support requires new guzzle versions.
v13 sets requirements to PHP 8.4 compatible
guzzle libraries versions, so v13 can not ship
with libraries lower than that. This drops
guzzle/promises v1 support, which has been
re-added to v12 for backwards compatible
reasons, and v13 inherited this. It should be
fair to drop guzzle/promises v1 in v13 now.

v12 and v11 will only "composer u" to the
versions below, but not require them, so
non-composer releases will package compatible
library versions, while composer instances
have the option to update when needed.

> composer u guzzlehttp/guzzle guzzlehttp/promises guzzlehttp/psr7

Resolves: #104488
Releases: main, 12.4, 11.5
Change-Id: I43a4e56f9fbb3bb00d77eb198161350e72a51da4
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85395


Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

Brings PHP 8.4 fixes.

"composer req" in v13, "composer u" in v12 and v11.

> composer u typo3/html-sanitizer

Resolves: #104483
Releases: main, 12.4, 11.5
Change-Id: I3c5dfb7eb1b76bc13ef0d784e87138360bfbdd61
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85392


Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

This change raises the core-testing-php84
image version to use PHP 8.4.0 alpha2.

[1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/abd0b88dd70d0053359b08584d66df17540f177d

Resolves: #104480
Releases: main, 12.4, 11.5
Change-Id: Ife69d5fdb82f4243547fab5998b4a1ba0123bafc
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85357


Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

phpstan "bleeding edge config" enables a feature that
reduces memory usage significantly. We don't switch
to "bleeding edge" per se, but enable that single
toggle for now. phpstan does not do this by default
since it may be breaking for existing rules, which is
not a problem in our case.

> rm -rf .cache/phpstan/; Build/Scripts/runTests.sh -s phpstan

Before locally: 10.99 GB
After locally: 5.82 GB
Before CI: 15.15 GB
After CI: 9.49 GB

Numbers vary depending mainly on available number of CPUs:
My local machine has less CPUs than CI - we *may* tune
phpstan a bit further in this area, later.

Resolves: #104476
Related: #104475
Releases: main, 12.4, 11.5
Change-Id: I32ca9a36b752ad52e8ac5fd433c3f929f86843af
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85378


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Stefan Bürk <stefan@buerk.tech>

phpstan can be very memory hungry. Option --verbose
adds a line about 'peak memory' usage to the output.
Add this to get a better feeling of the memory usage.

Resolves: #104475
Releases: main, 12.4, 11.5
Change-Id: I3fdaf7ddee7e003e7a8e75a508dd69161c804c8d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85354


Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

This commit updates the package `requirejs` to version 2.3.7 to fix a
prototype pollution vulnerability [1].

[1] https://github.com/requirejs/requirejs/compare/2.3.6...2.3.7

Resolves: #104459
Releases: 12.4, 11.5
Change-Id: I73a62c7e4e715954db5802d0a46d5758c407ac7a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85335


Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>

Resolves: #104435
Releases: main, 12.4, 11.5
Change-Id: I5ff37f97f0d0a71420839c4d2b1bf8bde70afa7f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85206


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

This change adds the predefined GitLab CI/CD variable
`CI_JOB_ID` value to the suffix, used for containerized
network and container names, with the goal to increase
uniqueness in CI runs.

Additionally, the value is now displayed in execution
and the container cleanup notes at least the network
name further information source to investage unusually
container shutdowns.

[1] https://docs.gitlab.com/ee/ci/variables/predefined_variables.html

Resolves: #103928
Releases: main, 12.4, 11.5
Change-Id: I6cf8dddefd2b45ed6f5c8cca8aa5521319cc8c4b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85302


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>

Fixes an array key warning in $backendUser->groupData['webmounts'].

Resolves: #104430
Releases: main, 12.4, 11.5
Change-Id: I077c59c67067f6221288ca4a73589dcc9c69bd07
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85298


Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

Do not listen on the livereload port, as we do not ship
the client-side[1] livereload integration anyway.

This allows multiple grunt-watch (e.g. main and 12.4) to run
in parallel instead of blocking each other because they try
to allocate the same port.

[1] https://github.com/gruntjs/grunt-contrib-watch/blob/main/docs/watch-examples.md#enabling-live-reload-in-your-html

Resolves: #104390
Releases: main, 12.4, 11.5
Change-Id: I36f37178e1752015033d5b0f2746c49b2477c1a2
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85201


Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Kienast <a.fernandez@scripting-base.de>

PHP 8.4 linting is fine already.
Let's add it to CI jobs.

Resolves: #104386
Releases: main, 12.4, 11.5
Change-Id: Ie64f602aace5d816ae80ce502bdf054dde7b787a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85253


Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>

Brings PHP 8.4 fixes.

Hard raise in v13, "composer u" in v12 and v11.

> compser u psr/http-factory

Resolves: #104384
Releases: main, 12.4, 11.5
Change-Id: I65b5955379e30c4f889ed76d0b211ae25c83057d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85249


Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

BcryptPasswordHash has an option to set a cost
value. The lower barrier used to be identical
to PHP constant PASSWORD_BCRYPT_DEFAULT_COST.

Tests use the lower barrier to speed up tests.
With PHP <8.4, PASSWORD_BCRYPT_DEFAULT_COST is
10, it has been raised to 12 with PHP 8.4.

The patch frees our code from access to this
constant and hard codes 10 as lower barrier
check. This keeps the API as is, and this hash
is by default set to 12 already in default
options if none are provided.

Resolves: #104373
Releases: main, 12.4, 11.5
Change-Id: I4c1e94fdc50aa3075570549ccdd3b81a2de2e98a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85237


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>

As a PHP 8.4 preparation, phpunit is raised
to latest version of current major version.

Note 11.5 needs a raise of nikic/php-parser
as well, which we do not require, but raise
within lock files only.

> composer u nikic/php-parser
> composer req --dev phpunit/phpunit:^9.6.20 -w

Resolves: #104372
Releases: main, 12.4, 11.5
Change-Id: I395b8487bc3aca2dc34d4b7fe86c03d58a7a8709
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85234


Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

Bump dependency to latest 1.0 patch level to gain
PHP 8.4 support. Do not raise in composer.json to
not disturb existing instances.

> composer u lolli42/finediff

Resolves: #104340
Related: #104339
Releases: 12.4, 11.5
Change-Id: I8017bc89186ed1496bcaa509978163582857a285
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85185


Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>