Fix in remote_operations_handler.py functions

[MARCOSD4]

Description

This PR aims to make the necessary changes in the code to avoid that the Vulnerability Detector E2E tests do not continuing if any error occurs during the setup of some of the agents, that is to say, if any error occurs during this phase, the execution must continue to allow the development of the rest of the agents. For this purpose, some functions of the remote_operations_handler.py script have been modified, since the problem was detected in them because, in the event of an error, they terminated the execution of the function using raise error. They have been modified so that they do not terminate the execution but simply report the error and continue the process.

The functions install_package, remove_package, and update_package have been modified, since although these last two are not currently executed during setup, they also produce the same error during the development of the body tasks and therefore if they fail for one system, the execution would not progress for the rest.

Testing performed

The upgrade_package_maintain_vulnerability test was run on the environment https://ci.wazuh.info/job/Wazuh_QA_environment/1038/ and the results are as follows:

report5097.zip

[Rebits]

Good job overall. However, there are a couple of issues that need to be addressed:

• The current approach doesn't prevent the test case from running for endpoints that failed in the setup phase, leading to inefficient testing.
• It's noted that these functions will undergo refactoring in the future to address code coupling.

Despite these concerns, we'll proceed with these changes for now. This will enable us to generate a comprehensive report for all endpoints, even in failure cases