Improve release system

[dedece35]

please take into account following optimizations for automatic release system :

• really change the version of plugin deployed, thus the real version will appear in administration SonarQube UI
• optimize generated release notes from changelog : actually, release notes are generated from text between 2nd H2 and 3rd H2.
  • add tag pusher login
  • add commiters list
• make documentation about this system (how it works, how to make a release)
• protect tag creation and deletion : https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules

[dedece35]

• ✅ really change the version of plugin deployed, thus the real version will appear in administration SonarQube UI
  • protect execution of manual tagging system
  • protection against direct commit on mainbranch is a problem for mvn release:prepare command
• 🟥 OPTIONAL - optimize generated release notes from changelog : actually, release notes are generated from text between 2nd H2 and 3rd H2.
  • add tag pusher login
  • add commiters list
  • check process to verify that a title with actual version is present before anything else
• ✅ make documentation about this system (how it works, how to make a release)
• ✅ protect tag creation and deletion : https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules

[dedece35]

issue corrected with release 0.2.0 (https://github.com/green-code-initiative/ecoCode/releases)