Create daemon handler fixture for integration test

[Rebits]

Related issue
#1825

Description

This PR closes #1825. It adds a common Wazuh daemon handler fixture for all integration tests, according to the repository standard

Usage

In order to use this fixture, the test should define the following dictionary at the beginning of the module:

daemons_handler_configuration = {'daemons': ['wazuh-remoted'], 'ignore_errors': True}

In case of the required of restart all wazuh, it is possible to use wazuh_control using the following configuration

daemons_handler_configuration = {'wazuh_control': True, 'ignore_errors': True}

Where:

• daemons (list): List of daemons to use. If empty, all wazuh will be used.
• wazuh_control (boolean): Enable restart of all wazuh services using wazuh_control.
• ignore_errors (boolean): Enable ignore errors in daemon handling process.

Tests

• Proven that this fixture works correctly

• Python codebase satisfies PEP-8 style style guide. pycodestyle --max-line-length=120 --show-source --show-pep8 file.py.
• Python codebase is documented following the Google Style for Python docstrings.

[Selutario]

Additional info

In the case of creating a variable with the necessary daemons for the API to work, the list is as follows:

• wazuh-apid
• wazuh-modulesd
• wazuh-analysisd
• wazuh-execd
• wazuh-db
• wazuh-remoted

If any of those daemons are not ready, the error below will be returned for any API request:

{
  "title": "Bad Request",
  "detail": "Some Wazuh daemons are not ready yet in node \"master-node\" (wazuh-modulesd->stopped, wazuh-analysisd->stopped, wazuh-execd->stopped, wazuh-remoted->stopped)",
  "dapi_errors": {
    "master-node": {
      "error": "Some Wazuh daemons are not ready yet in node \"master-node\" (wazuh-modulesd->stopped, wazuh-analysisd->stopped, wazuh-execd->stopped, wazuh-remoted->stopped)"
    }
  },
  "error": 1017
}

Regards.

[jmv74211]

Good job. Some changes are requested.

Note: I have observed that you put some debug logs. This fixture will be called in every test for each use case, so these debug logs can be very noisy. Take this into account.

[Rebits]

Respecting to this comment, yes, that could be an issue, but IMHO it is important to begin to include some verbose in our testing procedure. Maybe it would be necessary to create a new logs levels and implement tools to handle the log-cli-level, log-file-level and log-file of pytest.

[juliamagan]

LGTM

[juliamagan]

We can test these changes before the merge in temporal branch: common-fixtures-testing

[jmv74211]

Can you change this for all_daemons or something similar. wazuh_control is a bit confusing