feat: init fluidPrices for latest data

Related to #525 (closed)

🚩 Give your MR title the same name that the desired squash commit. In doubt, check the conventional commit doc. examples
feat(profile): add...
fix(annuaire): remove...

What does this MR do and why?

Launch fluidPrices service during initialization to make sure last data has valid price

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally (or on alpha)

⚠ Check on Alpha as launching services locally with `cozy-konnector-dev` doesn't create triggers

1. Deploy on an Alpha instance
2. Make sure to have some fluid connected
3. Change last price for one or more fluid on https://ecolyo-agent-rec.apps.grandlyon.com/prices (put something noticable i.e. 10€/kWh)
4. Reload your instance, wait a few seconds for the service to end (it is run asynchronously)
5. Check the last days of data for your fluid you should see the new prices

MR acceptance checklist

To be completed by the chosen reviewer.

Quality -

• For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
• I have made sure that the sonar quality coverage is up to standards.
• I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
• I have tested this MR in all supported browsers or determined that this testing is not needed.
• I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.

Performance, reliability and availability

• I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
• I have considered the scalability risk based on future predicted growth.

Documentation

• The MR is named after the desired squash commit to feed the changelog linked to the current milestone.
• I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.

Security

• I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.

Deployment

• When featured on a self-data project release, I have made sure my app version in the manifest and package.json is incremented and any relative changes to the permissions are clearly written and transmitted to Cozy.

Related to #525 (closed)