Maintain production and numbered branches post release 4.5.2 in wazuh-packages repository

[davidjiglesias]

Description

The goal is to complete the following tasks, each task must have a PR associated with this issue.

The branches must follow the naming: merge-<ORIGIN_BRANCH>-into-<DESTINATION_BRANCH>. For example, merge-4.5.2-into-4.5.3.

Tasks

• Merge branch 4.5.2 into branch 4.5.3.
• Merge branch 4.5.3 into branch 4.6.0.
• Merge branch 4.6.0 into branch 4.7.0.
• Merge branch 4.7.0 into branch master.
• Delete all stage pre-releases for 4.5.2 (https://github.com/wazuh/wazuh-packages/releases).
• Delete all stage tags for v4.5.2. BE CAREFUL NOT TO DELETE DEFINITIVE TAG. Example: v4.5.2-rc1, 4.5.2-alpha1, etc.
• Delete branch 4.5.2.

[DFolchA]

Update

• 4.5.3 -> No changes
• 4.6.0 -> Merge 4.5.3 into 4.6.0 #2426
• 4.7.0 -> Merge 4.6.0 into 4.7.0 #2427
• master -> Merge 4.7.0 into master #2428

[vikman90]

We cannot delete branch 4.5.2 until #2366 targets to another base branch.