Add a hook 'actionValidateOrderBefore' called before actionValidateOrder

[bibips]

Questions	Answers
Branch?	develop
Description?	Add a new hook 'actionValidateOrderBefore'. This hook is called before the creation of an order
Type?	new feature
Category?	FO
BC breaks?	no
Deprecations?	no
How to test?	From a module register the hook and create the function hookActionValidateOrderBefore
UI Tests	https://github.com/bibips/ga.tests.ui.pr/actions/runs/6709834106
Fixed issue or discussion?	Fixes #34432

When the order tunnel is customized with additional steps, developers need to verify the data entered by the user within the tunnel steps.
It is of course possible to verify this data at each stage of the order tunnel, but it is also preferable to check the integrity of the data just before confirming the order.

For example, in the case of an order tunnel stage where the customer can enter a date in the future, it is necessary to check this date again when the customer confirms the order. This check avoids data inconsistencies when the customer confirms his basket several days after creating it.

[prestonBot]

Hi, thanks for this contribution!

I found some issues with the Pull Request description:

• Your pull request does not seem to fix any issue, consider creating one (see note below) and linking it by writing Fixes #1234.

Would you mind having a look at it? This will help us understand how interesting your contribution is, thank you very much!

About linked issues

Please consider opening an issue before submitting a Pull Request:

• If it's a bug fix, it helps maintainers verify that the bug is effectively due to a defect in the code, and that it hasn't been fixed already.
• It can help trigger a discussion about the best implementation path before a single line of code is written.
• It may lead the Core Product team to mark that issue as a priority, further attracting the maintainers' attention.

(Note: this is an automated message, but answering it will reach a real human)

[florine2623]

I think this should be QA by dev

[matks]

Tested using https://github.com/PrestaShop/ps_qualityassurance

[matks]

Thank you @bibips

[gericfo]

Hello @bibips
Please note that the “Needs autoupgrade PR” label has been automatically added to your Pull Request. This means that the changes made in your PR must also be reported in the Autoupgrade module, responsible for running the update process of PrestaShop stores.
When there's a modification to the db-structure.sql file or if a Doctrine entity has been modified, added, or deleted, it impacts the database structure. Modifying the list of hooks and feature flags has consequences on the update process as well. These changes can affect how the application interacts with the database and how update procedures are handled. It's important to consider these aspects when contributing to ensure a smooth update experience for users.
That's why this contribution should be backported, with another corresponding PR, on the Autoupgrade module's GitHub repository which is available here: link.
Don't forget to add a comment in this current thread with the link to this PR once it has been created.
Thank you.

[bibips]

@gericfo I opened the PR PrestaShop/autoupgrade#981

[gericfo]

Thanks @bibips!