In top-level "pom.xml", use new versions for "commons-configuration2" and "commons-beanutils" to avoid logging a stack trace

In "ProjectView", avoid exception by testing if value for config key ""History.lastUsedProject" is the empty string

"TargetPedestrian.getId()" is now used by "TargetChangerController" to implement follower behavior.

Furthermore, deleted unnecessary code in following files:
- VadereSimulator/src/org/vadere/simulator/models/osm/OptimalStepsModel.java
- VadereSimulator/src/org/vadere/simulator/models/osm/PedestrianOSM.java

Fixes issue #267.

VadereSimulator/src/org/vadere/simulator/models/osm/OptimalStepsModel.java:
- Added TODO to use new list "Agent.getFollowers()".

Added boolean variable "isCurrentTargetAnAgent" to "Agent" and use it in "TargetChangerController" and "PedestrianOSM"

Added binomial distribution to "TargetChangerController" and added test scenarios for "TargetChangerController"

Deleted non-working scenario "TestSpeedInAreaProcessor-SpeedByTrajectory.scenario" (does not work anymore after merging with master)

But three scenarios still throw exceptions:
- 11-RiMEA11-ExitSelection-OSMEventDriven-SBEnabled:
  ClassCastException: TimestepPedestrianIdKey cannot be cast to EventtimePedestrianIdKey
- TestSpeedInAreaProcessor-SpeedByTrajectory:
  ClassCastException: FootStepProcessor cannot be cast to class FootStepProcessor
- TestSpeedInAreaProcessor-SpeedByWidth:
  ClassCastException: FootStepProcessor cannot be cast to class FootStepProcessor and PedestrianVelocityDefaultProcessor are in unnamed module of loader 'app'

Use FootStepProcessor in Postviz and as default trajectory output processor

Closes #253

See merge request !85

VadereGui/src/org/vadere/gui/postvisualization/view/SettingsDialog.java:
- This class placed Bene's criteria coloring pane and the "colorize by
  evacuation" checkbox time at the wrong position. Parent class "SettingsDialog"
  offers two getters now to retrieve the correct position for both elements.