Resolve "[2] [Fluides] Enlever croix rouge sur connecteur quand problème lié au partenaire ou au compteur"

Related to #470 (closed)

What does this MR do and why?

• Croix rouge en haut : la croix rouge sur le connecteur en haut ne doit s'afficher que si problème de connexion avec l'API du partenaire. Elle ne doit pas s'afficher si seulement "retard de données".
• Couleur "Données manquantes" : Passer les mots "données manquantes" en blanc (= couleur normale)
• Créer un status de type "Warning" (nouveau picto). Ce statut n'induit pas de picto sur le picto du fluide en haut mais un encart spécifique en bas quand on va voir les infos sur le connecteur. Cf maquettes
• On laisse bien sur le "dernière donnée disponible..." tel que fonctionnant actuellement.
• Mettre à jour la documentation en conséquence : https://doc.self-data.alpha.grandlyon.com/ecolyo/functionalities/consumption/#dataload-consumption-visualizer

Screenshots or screen recordings

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

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 #470 (closed)