Post release tasks for 4.9.0

[juliamagan]

Description

This issue attempts to track the steps necessary to complete post-release maintenance tasks for 4.9.0. 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.9.0-into-4.9.1.

Tasks

• [x] Merge branch 4.9.0 into branch 4.9.1.

  It is not required because it is synced

• [x] Merge branch 4.9.1 into branch 4.10.0.

  It is not required because it is synced

• [x] Merge branch 4.10.0 into branch master.

  Created master-2.16.0 branch from 4.10.0 and adding 860d4020613ded14b4c23a141b153b54de6088d9 commit Created backup of current master branch master-2.12.0 master-2.16.0 branch renamed to master

• [x] Publish GitHub release as latest.
• [x] Delete all stage pre-releases for 4.9.0 (https://github.com/wazuh/wazuh-security-dashboards-plugin/releases).
• [x] Delete all stage tags for v4.9.0. BE CAREFUL NOT TO DELETE DEFINITIVE TAG. Example: v4.9.0-rc1, 4.9.0-alpha1, etc.