Fixed bug: the ARA client did create routing table entries to its own location

The problem arose when a client started a route discovery by
broadcasting a FANT. This FANT would be rebroadcasted by the any
neighbor node in thus be received by the original source node.
The source node must ignore those packets instead of creating a
routing table entry to its own location.

I did also add a test to make sure this bug does not reappear in the
future :)
Only some small comments
Removed some unnecessary getter and setter from the rounnecessary getter and setter from the routing table
Minor modification to the IDE settings
Introduced the concept of a Configuration class (not yet used)
Removed the dependency between PathReinforcementPolicy -> RoutingTable.

There was also a violation of the SRP. Everything is now nice, easy and
clean :)
The path reinforcement for received packets is now also done by the PathReinforcementPolicy
Removed one of the ignored test: hard to test the static environment (lives longer than the tests)
Some cleanup of unnessecary dependencies for the ForwardingPolicy
Merge branch 'configuration' into develop
Some code cleanup
Added more configuration options
Created the OMNeTConfiguration which holds the logic for reading the configuration parameters from OMNeT++
added classes for EARA
added unit test for class EnergyAwareRoutingTableEntry
added delete call in destructor of class OMNeTARA for member evaporationPolicy
provided implementation for class EnergyAwareRoutingTable
fixed memory leak in class RoutingTable
added unit test for class EnergyAwareRoutingTable
added header files for classes AbstractEARAClient and OMNeTEARA