Windows agent must not start with WAZUH_MANAGER and WAZUH_REGISTRATION_SERVER used together

[alberpilot]

The Windows Wazuh agent has a different behavior than Linux one using deployment variables. The Linux installer always needs to manually start the service. On the other hand, the Windows installer has the case where using WAZUH_REGISTRATION_SERVER with WAZUH_MANAGER is able to automatically start the service.

We need to change this behavior by:

• Modifying the Windows deployment variable script for not to start the agent with this variables combination.
• Modify the Wazuh kibana app to include a new step starting manually the service.
• Modify the Documentation in the same way.
• Modify the Cloud documentation accordingly.

[alberpilot]

Cloud team asked. No modifications are needed from his side.