fix: update styles (buttons, inputs...)

Related to #532 (closed)

How to review

This is a pretty big MR, you don't have to check each change but rather check all screens and modal in the application (you can also check changes outside /components folder. I'll also have this MR go through the design to make sure everything is ok.

What does this MR do and why?

This was all variants of buttons across the app

Tasks

• supprimer les margins globales des button. Un élément ne dois jamais influer sur son espacement avec les autres
• Primary -> 0 border
• Primary inverted -> dégradé + supprimer l'opacité bizarre
• a0a0 -> supprimer, utiliser e0e0
• tous les textes + contours -> e0e0
• bouton secondaire -> supprimer
• bouton tertiaire -> devient le secondaire
• bouton "Voir plus" -> transformer en bouton
• modales boutons sur une seule ligne si place suffisante ou sinon **bouton primary au dessus **
• bouton précédent avec "< Précédent" -> supprimer les flèches "<" ">"
• input -> border soft-grey & yellow si actif
• checkbox -> border gris
• update de la section alerte fuite d'eau
• enlever les doublons de styles dans les form de connection

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)

List all steps to set up and validate the changes on local environment.

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.