[TASK] add respond(d) daemon

[genofire]

fix #156

a proof of concept

---

• implements
  • mac from "main" interface
  • nodeinfo-software-babel wait for publish Version in babel parser refactory: remove strange type Id + publish BabelDesc.Version Vivena/babelweb2#11
• unittests
• docu

[codecov-io]

Codecov Report

Merging #157 into master will decrease coverage by 13.27%.
The diff coverage is 1.76%.

@@             Coverage Diff             @@
##           master     #157       +/-   ##
===========================================
- Coverage   75.05%   61.78%   -13.28%     
===========================================
  Files          52       62       +10     
  Lines        1772     2151      +379     
===========================================
- Hits         1330     1329        -1     
- Misses        404      784      +380     
  Partials       38       38

Impacted Files	Coverage Δ
respond/daemon/statistics.go	0% <0%> (ø)
respond/daemon/batman.go	0% <0%> (ø)
cmd/serve.go	9.09% <0%> (ø)	⬆️
respond/daemon/main.go	0% <0%> (ø)
respond/daemon/config.go	0% <0%> (ø)
respond/daemon/handler.go	0% <0%> (ø)
respond/daemon/nodeinfo.go	0% <0%> (ø)
cmd/import.go	12% <0%> (-1.05%)	⬇️
respond/daemon/neighbours.go	0% <0%> (ø)
respond/daemon/data.go	0% <0%> (ø)
... and 14 more

[belzebub40k]

@genofire What do you think about an option to specify from which interface(s) to read the IP addresses? Currently only the IPs from the interface on which the request was received is listed for servers with interfaces in multiple meshes. It would be nice to have either the loopback addresses or all mesh IPs listed.