Is the Overload case with 100% drop and high latency a potential source
for strange behavior or assures a 100% drop that alle msgs are really
dropped?

Merge Master into nr/monitoring-model

See merge request !4

- graph hopper needs a temp-folder with a file lock. The new setting
MOVEMENT_GRAPH_UNIQUE_FOLDERS can be used to force unique folders for
the temporary data. Remember to purge the osm folder manually every now
and then, as this will lead to large amounts of temp data in batched
runs.

- e.g., use Delta_* to filter for all metrics with a name starting with
"Delta_"
- Added an ActiveComponent filter, that utilizes a LifecycleComponent's
isActive() method to invalidate metrics for inactive hosts
- added STD to measurementStatistics DAO

Merge branch 'nr/monitoring-model' of dev.kom.e-technik.tu-darmstadt.de:simonstrator/simonstrator-peerfactsim into nr/monitoring-model

Merge Master into nr/monitoring-model

See merge request !2

Rewrote Visualization. Rewrote menu creation. Added periodic repainting. Fixed getStatus(). Removed overload debug output.

- Attraction Points with weights and radii
- Local movement with correct speed in scaled scenarios
- New weighted transition strategy for local movement