… and serializer configuration

* 5.4:
  [Tests] Streamline
  [Validator] updated Romanian translation

* 6.3:
  [Console] Fix horizontal table top border is incorrectly rendered
  [Tests] Streamline
  [Uid] Fix UuidV7 collisions within the same ms
  [Validator] updated Romanian translation

…o avoid false positives

Fixes symfony/symfony#52433

… schedule (valtzu)

This PR was merged into the 6.4 branch.

Discussion
----------

[FrameworkBundle][Scheduler] Add test for autoconfigured schedule

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| License       | MIT

Add functional tests for autoconfigured schedules / tasks, as discussed in symfony/symfony#51525 (comment).

Commits
-------

ea2a8cd7255 Add test for autoconfigured schedule

…hich callables are legit controllers when the `_check_controller_is_allowed` request attribute is set

…r console commands (keulinho)

This PR was merged into the 6.4 branch.

Discussion
----------

[Console][FrameworkBundle] Fix missing `profile` option for console commands

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Issues        | Fix symfony/symfony#52433
| License       | MIT

Commits
-------

0e0848bc27 Fix missing `profile` option for console commands

…()` to define which callables are legit controllers when the `_check_controller_is_allowed` request attribute is set (nicolas-grekas)

This PR was merged into the 6.4 branch.

Discussion
----------

[HttpKernel] Add `ControllerResolver::allowControllers()` to define which callables are legit controllers when the `_check_controller_is_allowed` request attribute is set

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Issues        | -
| License       | MIT

Right now, when one doesn't configure properly their APP_SECRET, this can too easily lead to an RCE.

This PR proposes to harden security by rejecting any not-allowed controllers when the `_check_controller_is_allowed` request attribute is set. We leverage this in FragmentListener to close the RCE gap.

In order to allow a controller, one should call `ControllerResolver::allowControllers()` during instantiation to tell which types or attributes should be accepted. #[AsController] is always allowed, and FrameworkBundle also allows instances of `AbstractController`.

Third-party bundles that provide controllers meant to be used as fragments should ensure their controllers are allowed by adding the method call to the `controller_resolver` service definition.

I propose this as a late 6.4 feature so that we can provide this hardening right away in 7.0. In 6.4, this would be only a deprecation.

Commits
-------

893aba9032 [HttpKernel] Add `ControllerResolver::allowControllers()` to define which callables are legit controllers when the `_check_controller_is_allowed` request attribute is set

* 6.3:
  [FrameworkBundle] Don't reference SYMFONY_IDE env var in non-debug mode
  wire the secret for Symfony 6.4 compatibility