Feature/improve ci

[Turiok]

Proposed changes

Ajoute la création d'une nouvelle intégration continue.
d'une release automatique via des github actions. Modifie aussi l'IC de base en ajoutant une analyse SonarQube. Ajoute aussi un dependabot.

Types of changes

What types of changes does your code introduce to i-Code?

Put an x in the boxes that apply

Ajout ou refonte de :

• Ajoute un workflow de release automatique qui va pousser les packages sur Github et créer une release note.

• Refonte de la CI sur push et PR avec ajout de scan SonarQube sur SonarCloud

  • Il faudra créer un projet SonarQube sur le Cloud, modifier le fichier sonar-project.properties en respectant les éléments du projet créé sur SonarQube.
  • Ajouter un token SonarQube et le mettre dans les github actions avec le nom 'SONAR_TOKEN'

• Pas mal de nettoyage au niveaux des pom.xml sur des properties inutiles

• **Attention : Suppression du code qui génère le plugin Eclipse. Ce code n'était plus maintenu depuis des années. **

• Un dependabot pour Github CI sur les dépendances Maven et les github actions

• Bugfix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

• Documentation Update (if none of the other choices apply)

Issues closed by changes

List here all issues closed by your changes. Use a list of items like - [x] Close #0

• Close #0

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• SonarCloud and GitHub Actions tests pass with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...