feat(admin): list all CNFS from Espace Coop

Related to #210 (closed)

What does this MR do and why?

Nouvel onglet admin pour visualiser :

1. Les CNFS chez Espace Coop qui n'ont pas de compte Rés'in
2. Les CNFS Rés'in qui ne sont pas référencés chez Espace Coop

🔈 Montée de la version de docker pour les pipelines (18.09 => 24.0.2)

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)

From server :

• Edit espaceCoop.service.ts line 26 to @Cron(CronExpression.EVERY_MINUTE) to launch the service that fetch and process CNFS from Espace Coop
• Check in db espacecoopcnfs collection
• Modify a user in your DB to have an email present in espacecoopcnfs
• Make sure to also have a Resin CNFS whose mail is not in espacecoopcnfs

From client:

• Launch client, connect as admin and visit 'CNFS Espace Coop' tab

---

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.

Related to #210 (closed)