Move tests out of harms way (=out of the source code dir)

Tests is great, and keep the tests organized in the same way as the
source is a good thing. But it's much easier to keep the tests in a
separate directory, but keep the structure as the soruce directory,
to see what is tested.

Change-Id: I874c47474a8a8204d0f5eb10cafb8982be330262
Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Worker: break out to a seperate subproject.

Keeping workers and lot of perferical stuff embedded in the code
base, it's much harder to port and change stuff. To be able to
rewrite it to handle multiple configurations at the same time, lot of
stuff needs to be rewritten. That means, it's much easier to keep the
codebase splitted up.

Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Remove include-everything-headers

Include-everything-headers makes it alsmost impossible to track
dependencies, when trying to refactor. It's not that hard when you
develop to actually include the nessecary files when using a new
header. And when including a new header you can actually think about
if it's a good idea to use that header in that particular source
file. That in helps making the code more structured.

There is actually almost nothing good by having those
include-everything-headers.

Change-Id: I8e0e0977bb16fa09c212792c218e6ecf9024a254
Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Cleanup files not realted to this procject/version anymore

Because lot is going to change, those files won't be relevant
anymore, so clean whose up to increase speed of grep:ing in the repo,
and don't trigger lot of false posisive matches when grepping

Change-Id: Id956339285517c0dff65ee3a99724c916761cf15
Signed-off-by: Max Sikstrom <msikstrom@op5.com>