Fix agent auto-restart when shared configuration changes

[vikman90]

On RHEL 9 on containers, service links to systemctl but that's unavailable.

Related issue
Closes #13602

This PR aims to let the Active Response script restart.sh behave just like restart-wazuh: simply call wazuh-control restart, no matter the underlying service manager.

Tests

• The agent is able to restart on an RHEL 9-based container after a shared configuration change.

Systemd service behavior

• Starting the agent through systemctl:

● wazuh-agent.service - Wazuh agent
   Loaded: loaded (/etc/systemd/system/wazuh-agent.service; enabled; vendor preset: disabl>
   Active: active (running) since Wed 2022-06-15 12:11:18 CEST; 1s ago
  Process: 12262 ExecStart=/usr/bin/env /var/ossec/bin/wazuh-control start (code=exited, s>
    Tasks: 34 (limit: 11405)
   Memory: 132.5M
   CGroup: /system.slice/wazuh-agent.service
           ├─12289 /var/ossec/bin/wazuh-execd
           ├─12298 /var/ossec/bin/wazuh-agentd
           ├─12312 /var/ossec/bin/wazuh-syscheckd
           ├─12322 /var/ossec/bin/wazuh-logcollector
           └─12337 /var/ossec/bin/wazuh-modulesd

• Agent auto-restart due to configuration change:

● wazuh-agent.service - Wazuh agent
   Loaded: loaded (/etc/systemd/system/wazuh-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2022-06-15 12:11:18 CEST; 16min ago
  Process: 12262 ExecStart=/usr/bin/env /var/ossec/bin/wazuh-control start (code=exited, status=0/SUCCESS)
    Tasks: 37 (limit: 11405)
   Memory: 538.2M
   CGroup: /system.slice/wazuh-agent.service
           ├─12471 /var/ossec/bin/wazuh-execd
           ├─12480 /var/ossec/bin/wazuh-agentd
           ├─12495 /var/ossec/bin/wazuh-syscheckd
           ├─12508 /var/ossec/bin/wazuh-logcollector
           └─12523 /var/ossec/bin/wazuh-modulesd

• Stopping the agent via systemctl:

● wazuh-agent.service - Wazuh agent
   Loaded: loaded (/etc/systemd/system/wazuh-agent.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Wed 2022-06-15 13:16:54 CEST; 4s ago
  Process: 9436 ExecStop=/usr/bin/env /var/ossec/bin/wazuh-control stop (code=exited, status=0/SUCCESS)
  Process: 8312 ExecStart=/usr/bin/env /var/ossec/bin/wazuh-control start (code=exited, status=0/SUCCESS)

• Starting the agent again:

● wazuh-agent.service - Wazuh agent
   Loaded: loaded (/etc/systemd/system/wazuh-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2022-06-15 13:17:26 CEST; 6s ago
  Process: 9436 ExecStop=/usr/bin/env /var/ossec/bin/wazuh-control stop (code=exited, status=0/SUCCESS)
  Process: 9507 ExecStart=/usr/bin/env /var/ossec/bin/wazuh-control start (code=exited, status=0/SUCCESS)
    Tasks: 38 (limit: 11405)
   Memory: 20.8M
   CGroup: /system.slice/wazuh-agent.service
           ├─9534 /var/ossec/bin/wazuh-execd
           ├─9543 /var/ossec/bin/wazuh-agentd
           ├─9558 /var/ossec/bin/wazuh-syscheckd
           ├─9571 /var/ossec/bin/wazuh-logcollector
           └─9619 /var/ossec/bin/wazuh-modulesd

[chemamartinez]

LGTM

[jmv74211]

QA review

• Type: Manual testing
• Status: Approved 🟢
• Testing issue: QA testing - Agent won't restart on containerized RHEL 9 wazuh-qa#3019
• Comments: While testing in docker, a problem has been found that it is necessary to install the ps command for Wazuh to work correctly. The following issue has been opened to report it. Otherwise, everything seems to work correctly.