Authd Tier 0: Several test fails

[Deblintrake09]

Related issue
#2923
#3022

Date	Commit	Nightly build	Build
2022-05-23	4b92ba1	https://ci.wazuh.info/job/test_nightly/1048/	https://ci.wazuh.info/job/Test_integration/26752/
2022-06-28	4a0c134	https://ci.wazuh.info/job/test_nightly/1077/	https://ci.wazuh.info/job/Test_integration/28178

Tier 0

• Cases

FAILED test_authd/test_remote_enrollment.py::test_remote_enrollment[no_remote_enrollment_standalone]
ERROR test_authd/test_authd_key_request_worker.py::test_authd_key_request_worker[Worker-forward-key-request-to-master-ip]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-add-agent]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-add-duplicate-agent-without-force-options-in-request]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-failed-duplicate-registration]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-force-registration]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-single/multi-group]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-remove-agent]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-agent-with-key-hash-simple]
ERROR test_authd/test_authd_local.py::test_authd_local_messages[authd_local_config-agent-with-key-hash-and-group]
ERROR test_authd/test_authd_worker.py::test_ossec_auth_messages[authd_worker_config-agent-message-with-key-hash-2]

• Description

During #2922 nightly, several test cases failed on Centos Manager.
Is required further research to determine the cause of the errors.

Systems Details

Manager System	Vagrant Box	Agent OS	Vagrant Box
Centos 8	qactl/centos8	Windows 10	gusztavvargadr/windows-10

[Deblintrake09]

Research results

• Failed test was caused by the previous case failing to restart wazuh and the environment being dirty because of that.
• Errors all came from control_service being unable to stop either clusterd or apid daemons. From research, it seems that it tries to stop the services getting the PID by name. The problem might be that the processes appear as python process instead of the actual process.
• A possible fix would be trying to stop the processes a different way. Still researching on a possible way.