Investigate and fix failed checks from upward merge

[MarcelKemp]

Wazuh version	Install type	Action performed	Platform
4.8.0	Manager	Install	-

Description

Checks have failed on the next merge upward PR for a variety of reasons, although all of these changes have been merged into 4.8.0 - Beta 1:

• Merge 4.8.0 into 4.8.1 #2814

We need to check the root of the problem and fix it so that the checks pass correctly.

Error details

• test-password-tool-success

  wazuh-passwords-tool.sh: line 340: /var/ossec/bin/wazuh-keystore: No such file or directory
  Unauthorized401
  Error: Process completed with exit code 1.

• All In One - Amazonlinux 2_base - Tests
• All In One - Rhel 9 - Tests
• Distributed Cases - manager_dashboard - centos - Tests
• Distributed Cases - manager_indexer - ubuntu - Tests

indexer-connnector: ERROR: HTTP response code said error, status code: 401

DoD

• Find the cause of the problems.
• Fix the issues encountered.
• Re-run the checks to verify that they are working correctly.

[tdrauncieal]

After an analysis of the logs provided by the related PR, it was found that the non-existence of the wazuh-keystore file is due to the fact that artifacts related to version 4.8.1 are being downloaded:

in which case the nonexistence of the tool is to be expected since it is part of version 4.8.0

[tdrauncieal]

The error reporting that the wazuh-keystore file does not exist was due to the fact that the package used for the installation, during the process, wazuh-manager_4.8.1-1_amd64.deb, was outdated.

test Reference: test-password-tool-success

However, the test persists returning an error, so the cause continues to be investigated.