Maintain production and numbered branches post release 4.5.2 in wazuh-kibana-app 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 4.5.2 into 4.5.3 #5856
• Merge branch 4.5.3 into branch 4.6.0. Merge 4.5.3 into 4.6.0 #5859
• Merge branch 4.6.0 into branch 4.7.0. Merge 4.6.0 into 4.7.0 #5860
• Merge branch 4.7.0 into branch master. Merge 4.7.0 into master #5861
• Delete all stage pre-releases for 4.5.2 (https://github.com/wazuh/wazuh-kibana-app/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.
• Merge branch 4.5.2-7.10 into branch 4.5.3-7.10. Merge 4.5.2-7.10 into 4.5.3-7.10 #5857
• Delete all stage tags for v4.5.2-7.10. BE CAREFUL NOT TO DELETE DEFINITIVE TAG. Example: v4.5.2-rc1, 4.5.2-alpha1, etc.
• Delete branch 4.5.2-7.10.
• Merge branch 4.5.2-7.16 into branch 4.5.3-7.16. Merge 4.5.2-7.16 into 4.5.3-7.16 #5858
• Delete all stage tags for v4.5.2-7.16. BE CAREFUL NOT TO DELETE DEFINITIVE TAG. Example: v4.5.2-rc1, 4.5.2-alpha1, etc.
• Delete branch 4.5.2-7.16.