Processes improvement tier 2

[davidjiglesias]

Description

This issue aims to unify processes and establish certain standards in order to improve the workflow of the development team in operational tasks, making them more efficient and reducing both resources and time spent.

Functional requirements

• As a development team member, I need a standardized version and revision format across all repositories to ensure consistency and predictability in version management. We should use our release stage format (alpha, beta, RC) as the revision identifier.
• As a development team member, I need a standardized changelog as well as, the standardized process for its update and review. We should use some kind of standard like https://keepachangelog.com/en/1.0.0/
• We wish to rename from 'master' to 'main' to align with modern naming conventions and inclusive practices.
• All operational tasks need to be automated using JobFlow within a Jenkins pipeline. The pipeline should handle various automated tasks, including supporting new stages and branches, managing the release protocol, etc. These pipelines will automatically create issue structures and update projects to carry on those tasks.

Plan

Automatization

• https://github.com/wazuh/wazuh-qa-automation/issues/82:

Standarization

• Version and revision standardization #5749

• Master branch rename across repositories #5750

• Changelog standardization across repositories #5751

• Stable branch standardization across repositories #5752