Adding HTTP server structure from aggregator

[joselsegura]

Description

HTTP server structure and very basic functionality copied&tuned from the aggregator.

Fixes #11

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update
• Refactor (refactoring code, removing useless files)
• Unit tests (no changes in the code)

Testing steps

Regular CI

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (master@4ed913a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #12   +/-   ##
=========================================
  Coverage          ?   19.30%           
=========================================
  Files             ?        9           
  Lines             ?      430           
  Branches          ?        0           
=========================================
  Hits              ?       83           
  Misses            ?      335           
  Partials          ?       12           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4ed913a...0b1d9a8. Read the comment docs.

[tisnik]

As this is partially also my code, LGTM :D

[Bee-lee]

you can tag and release v0.1:)

[natiiix]

LGTM
If it compiles, it's probably ok. 👍

[Serhii1011010]

I think it would be better to move it to a library or something

[joselsegura]

@tisnik partially? You are too humble :-D

@Sergey1011010 I tried a different approach, trying to define an "HTTPServer" interface or something, but at the end the TLS, authentication and CORS stuff will be only used in the smart proxy and not in the others HTTP servers, so I don't know if it has a lot of sense to put all of that in a common place