[Form][DateTime] Propagate invalid_message & invalid_message parameters to date & time sub widgets
bug #9453 [Form][DateTime] Propagate invalid_message & invalid_message_parameters to date & time (egeloen)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #9453).

Discussion
----------

[Form][DateTime] Propagate invalid_message & invalid_message_parameters to date & time

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

This PR propagates the `invalid_message` & `invalid_message_parameters` in the datetime form type to the date & time sub form types. It allows to have the good error message if you use something else than the `single_widget` widget.

I have looked the `DateTimeTypeTest` but I have not found tests related to this kind of propagation, so for now I have not added tests yet.

Commits
-------

ea4ae74 [Form][DateTime] Propagate invalid_message & invalid_message parameters to date & time sub widgets
[Finder] [Iterator] Make the tests less fragile
minor #12028 [Finder] [Iterator] Make the tests less fragile (AlphaStream)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #12028).

Discussion
----------

[Finder] [Iterator] Make the tests less fragile

Modified the Iterator tests so that they assert only on what's actually being tested. In particular, the tests were checking the order of the files [that were created virtually simultaneously] after sorting them by date. This change is a part of the effort to make Symfony successfully pass tests on HHVM

| Q             | A
| ------------- | ---
| Bug fix?      | [no]
| New feature?  | [no]
| BC breaks?    | [no]
| Deprecations? | [no]
| Tests pass?   | [yes]
| Fixed tickets | [none]
| License       | MIT
| Doc PR        | [none]

Commits
-------

10f9135 [Finder] [Iterator] Make the tests less fragile
Make Doctrine's dependency injection test less fragile.

[Doctrine][DependencyInjection] The test checks that a few items are ordered according to the value of their 'priority' attribute. However, a few of the items have the same value of this attribute. RegisterEventListenersAndSubscribersPass doesn't use a stable sorting, yet the test asserts that items that are 'equal' shall go in the original order. Modified so that the order of the original items is not checked.
minor #12058 [Doctrine][DependencyInjection] Make a test less fragile. (AlphaStream)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #12058).

Discussion
----------

[Doctrine][DependencyInjection] Make a test less fragile.

The test checks that a few items are ordered according to the value of their 'priority' attribute. However, a few of the items have the same value of this attribute. RegisterEventListenersAndSubscribersPass doesn't use a stable sorting, yet the test asserts that items that are 'equal' shall go in the original order. Modified so that the order of the original items is not checked.

| Q             | A
| ------------- | ---
| Bug fix?      | [no]
| New feature?  | [no]
| BC breaks?    | [no]
| Deprecations? | [no]
| Tests pass?   | [yes]
| Fixed tickets | [none]
| License       | MIT
| Doc PR        | [none]

Commits
-------

f1ae970 Make Doctrine's dependency injection test less fragile.
Merge branch '2.3' into 2.4

* 2.3:
  Make Doctrine's dependency injection test less fragile.
  [Finder] [Iterator] Make the tests less fragile
  [Form][DateTime] Propagate invalid_message & invalid_message parameters to date & time sub widgets
[SecurityBundle] fixed tests when used in standalone
Merge branch '2.3' into 2.4

* 2.3:
  [SecurityBundle] fixed tests when used in standalone
fixed some composer.json to make standalone component tests pass
fixed standalone component tests depending on Validator and Form
[Validator] fixed component standalone tests
fixed standalone tests
fixed standalone tests
[Debug] fixed class lookup when using PSR-0 with a target dir
minor #12071 [Debug] fixed class lookup when using PSR-0 with a target dir (fabpot)

This PR was merged into the 2.4 branch.

Discussion
----------

[Debug] fixed class lookup when using PSR-0 with a target dir

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

f5b38ec [Debug] fixed class lookup when using PSR-0 with a target dir
updated CHANGELOG for 2.4.10
updated VERSION for 2.4.10