Make the HttpClient class a common library

[TomasTurina]

Description

As part of the development of the new communicator, an HttpClient class was created to encapsulate HTTP calls to the Server Management and Agent Comms APIs.

Currently, this class is only available and adapted for use by the communicator component, but we will need to make it available to all modules as well. For this, we need to consider migrating the code of this wrapper to a common library and making it more generic, if necessary.

Also, as part of these changes, we also need to consider whether the communicator should be considered a module instead of a component, given all the tasks and responsibilities it has.

The following tasks should be performed:

• Separate the HTTPClient wrapper class into a common library.
• Share the wrapper with all modules so they can use it as well.
  • Multiple instances of the class can exist at once and work in parallel if possible.
• Analyze whether the communicator can be converted into a module and migrate its code to the src/modules folder if so decided.
  • It will be the responsibility of the ModuleManager to start it.

[TomasTurina]

Update

The HTTP client is now separated into a new project.

Boost Beast is now privately linked to the HTTP client project.

[TomasTurina]

Update

Working on migration of Co_PerformHttpRequest to communicator.

Code ready, missing tests.