Not start windows agent after installation with deployment variables

[DFolchA]

Related issue
wazuh/wazuh-packages#1249

Description

This PR removes the actions that start the windows agent if the deployment variables WAZUH_REGISTRATION_SERVER or AUTHD_SERVER are used.

With these changes the behavior of the windows agent will be the same as the Linux one when using the deployment variables.

Configuration options

Logs/Alerts example

Tests

• Compilation without warnings in every supported platform
  • Linux
  • Windows
  • MAC OS X
• Source installation
• Package installation
• Source upgrade
• Package upgrade
• Review logs syntax and correct language
• QA templates contemplate the added capabilities

• Memory tests for Linux
  • Scan-build report
  • Coverity
  • Valgrind (memcheck and descriptor leaks check)
  • Dr. Memory
  • AddressSanitizer
• Memory tests for Windows
  • Scan-build report
  • Coverity
  • Dr. Memory
• Memory tests for macOS
  • Scan-build report
  • Leaks
  • AddressSanitizer

• Retrocompatibility with older Wazuh versions
• Working on cluster environments
• Configuration on demand reports new parameters
• The data flow works as expected (agent-manager-api-app)
• Added unit tests (for new features)
• Stress test for affected components

• Decoder/Rule tests
  • Added unit testing files ".ini"
  • runtests.py executed without errors

[okynos]

LGTM