Since `Sleep` was not an option as discussed in
 #141, the waitGroup has been implemented in order to
make the program itself trigger the protocol methods
once a packet type in concrete is received.

Also, added state-vars in order to force the
`packetProcessor` gorutine to just activate the
waitGroup if a bootstrapping or network discovery
process is in progress.

Now we need to add timeouts in order to prevent the
app to get stucked at any protocol method execution.

On this way, we speed up the app by copying directly in the stack.

Now that we are using a different aproach with
waitgroups, we can get rid of this state variables.

Now the `Router` provides blocking methods to
poll Bootstrapp node and closestPeers (FIND_NODES)
to allow a better and more logical library construction
also featuring waitGroups and removing the timeouts.

Now that the `Router` offers blocking methods to
search for the closest `alpha` peers and for polling
the bootstrapping nodes, the logic can be leaved there
and the protocol functions just take car of the logic of
the algorithms itself.

We should not send the poll messages inside of the
afterFunc, instead, we should send the messages on
polling methods and wait on the afterFunc to execute
the getters to our tree.

With lower timings we should be able to get all
of the info we are expecting on the polling methods.