* 7.3:
  [HttpClient] Suggest amphp/http-client v5 by default
  [WebProfilerBundle] Fix typos in routing config deprecation messages
  cs tweak
  [FrameworkBundle] ensureKernelShutdown in tearDownAfterClass
  Revert "bug #60564 [FrameworkBundle] ensureKernelShutdown in tearDownAfterClass (cquintana92)"
  [Security] Keep roles when serializing tokens
  [JsonPath] Always use brackets notation with `JsonPath::key()`

* 7.3:
  Revert "minor #60377 [HttpFoundation] Emit PHP warning when `Response::sendHeaders()` is called while output has already been sent (ivo95v)"
  [Validator] Add missing HasNamedArguments to some constraints

* 7.3:
  [ObjectMapper] Fix test using LazyObjectInterface
  [Security] Fix added $token argument to UserCheckerInterface::checkPostAuth()
  minor #61192 [ObjectMapper] add missing legacy group (xabbuh)
  bugfix(#61139): Only generate an outputDir if none is set.

* 7.3:
  Add missing use statement for @param

* 7.3:
  [VarExporter] Fix serializing classes with __serialize() returning unprefixed private properties
  Remove direct access to internal properties cross-components

…dRoleMap` method (simonjamain-gp, simonjamain)

This PR was squashed before being merged into the 7.4 branch.

Discussion
----------

[Security] Improve performance of `RoleHierarchy::buildRoleMap` method

| Q             | A
| ------------- | ---
| Branch?       | 7.4
| Bug fix?      | no
| New feature?  | no (perf)
| Deprecations? | no
| Issues        | Fix #57322
| License       | MIT

use of an optimized role ustacking function

### What it does and why it's needed

_Note : Better in-detail explanation in there : https://github.com/symfony/symfony/issues/57322_
Uses the way faster `array_pop()` function to build the role map instead of `array shift`

### If it modifies existing behavior, include a before/after comparison

At first, it would look like this function swap could change slightly the ordering of the array produced by the `RoleHierarchy::buildRoleMap` method and it does it in a way. I find that it does not change the behaviour of our app.

I would not expect most other apps too break because I don't find many reasons to rely on the ordering of roles in hierarchies. Furthermore, `buildRoleMap` is a protected method serving the public `getReachableRoleNames` which does not imply a particular ordering (rightfully so IMHO).

### Testing

As it does not change or introduce any behavious per say, this performance increase rely on old tests passing again.
If I am not mistaken, the current `testGetReachableRoleNames()` still passes even tho it asserts a specific ordering. I still changed the assertion so it does not convey any false premises.

Commits
-------

508b62fd788 [Security] Improve performance of `RoleHierarchy::buildRoleMap` method