feat: Implement PHP client endpoints into Prestashop

[Benjamin-Freoua-Alma]

Reason for change

Linear task

Code changes

First part : CMS is able to send the endpoint_url to backend

We create a function in clientHelper to send url for gather cms data
We create a function in apiHelper to send url for gather cms data
We use the function to send url for gather cms data after the form saved

Second part : CMS is able to return cms_collected_data to backend

Blocked by the PR front controller CMS Data

How to test

As a reviewer, you are encouraged to test the PR locally.

First part : Save the config form and see if the url of front controller for gather CMS data is send
Second part : Execute the url executed by Alma and see if the CMS data are send

Checklist for authors and reviewers

• The title of the PR uses business wording, not technical jargon, for the changelog readers to understand it
• The PR implements the changes asked in the referenced task / issue
• The automated tests are compliant with the testing strategy
• The tests are relevant, and cover the corner/error cases, not only the happy path
• You understand the impact of this PR on existing code/features
• The changes include adequate logging and Datadog traces
• Documentation is updated (API, developer documentation, ADR, Notion...)

Non applicable

[Francois-Gomis]

Module name is not a Param - it a getAlmaModule methode and it's an AlmaModuleFactory

[Benjamin-Freoua-Alma]

@Francois-Gomis I'm not sure to understand your request. Can we speak on that in synchroniously

[github-actions]

⏳E2E tests are currently running.
➡️ You can follow their progression here.

[sonarcloud]

Quality Gate failed

Failed conditions
1 New Bugs (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[github-actions]

❌ E2E tests have failed.
➡️ You can find the results here.