Adapt Command Manager to the new design

[AlexRuiz7]

Description

After completing the initial 5.0 MVP iteration, the initial design of the Command Manager plugin is going to be adapted due to incoming changes on the Server (see wazuh/wazuh#27434). The Command Manager will no longer be responsible for searching, preparing and sending the commands to the Server. It will be the Server who queries the Indexer for the commands, greatly simplifying the data flow.

Key changes include:

• The Command Manager won't send commands to the Server. All code, settings, documentation and tests related must be removed as these won't be needed anymore.

• The Command Manager still needs to implement a Job Scheduler job. This job's responsibility is to look for commands which have expired, updating their status to FAILURE. The job's schedule is configurable. The condition could be modeled as:

  if (order.delivery_timestamp < current_timestamp) {
    order.setStatus(Status.FAILURE);
    order.save();
  }

Functional requirements

• Remove HttpClient module and delivery of commands.
• Remove settings related to the delivery of commands.
  • m_api.uri
  • m_api.username
  • m_api.password
• Adapt tests and documentation, removing what's necessary.

Plan

• Remove code relates to the delivery of commands.
  • HttpClient.
  • Settings.
  • Deliver of orders from the Job Scheduler job.
  • Related tests.
• Simplify SearchThread (job) to look for expired commands, updating their status.
• Provide queries for the API #210

Related issues

• Command Manager configuration file #180
• [BUG] The Command Manager re-autenticates on each request #192
• [BUG] The Command Manager sends the same command more than once #195
• Add Management API CA file field to opensearch.yml #171
• [BUG] testPost_success is flaky #163