Improve execution modes for Windows

[TomasTurina]

Description

As requested in #362, the goal of this task is to test and implement the necessary changes to run the new agent in the foreground on the Windows platform. Additionally, the logic for creating the wazuh-agent.lock file, as implemented on Unix systems, will be reviewed to determine its applicability to Windows.

Tasks

• Implement the required changes to run the agent in the foreground.
• Determine if the use of wazuh-agent.lock file should be applied to Windows.
• Implement necessary changes and appropriate testing.

[aritosteles]

Update

• 2025-01-15:
  Setting up environment
• 2025-01-16:
  Finished setting up the environment. Ran into some issues with warnings triggered as errors, had to use the W- flag to build. Started evaluating possible solutions for the issue at hand. Will investigate if SCM allows us to specify command line parameters so as to keep the behavior consistent with that of linux and macOS.
• 2025-01-17:
  Have a first attempt of a running agent in foreground. Having some trouble with impostor server-mock.
• 2025-01-20:
  Agent is running in the foreground.
  Modified Logger to print to stderr same as in linux agent.
  Looked into windows logger using single threaded sinks (as opposed to multithreaded sinks used in linux logger) and fixed it.
• 2025-01-21:
  Verified the agent is running both in foreground and as a service.
  Removed WindowsEventLog sink from logger and left only stderr sink when running in foreground.
  Working on implementing file lock mechanism in Windows.
• 2025-01-22:
  Implemented the instance lock using named mutexes for Windows. Separated unix/windows implementations each into their own files. Refactored LockFileHandler class into InstanceHandler to avoid references to any particular implementation.