Fix bug in collision checking of VPF

[dqyi11]

Fix the wrong way of calling StepSequence in collision checking of VPF.

• Document new methods and classes (N/A)

• Format code with make format

• Set version target by selecting a milestone on the right side

• Summarize this change in CHANGELOG.md

• Add unit test(s) for this change (N/A)

[dqyi11]

Now the test will fail because of a bug in the iterator of StepSequence.
StepSequence seq2(0.2, false); for (double v : seq2) { DART_UNUSED(v); count++; }

An exception will be throw

unknown file: Failure
C++ exception with description "Indexed maximum intenger." thrown in the test body.```

I created another PR #305 to fix it.

[jslee02]

The VFP test is still failing. Is this expected?

[jslee02]

Please move this to 0.3.0. 0.2.0 is released.

[dqyi11]

It is still failing for the same reason.
The issue in StepSequence is not fully addressed.
I will fix that.

[codecov]

Codecov Report

Merging #303 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #303      +/-   ##
==========================================
+ Coverage   81.01%   81.06%   +0.04%     
==========================================
  Files         204      204              
  Lines        6005     6005              
==========================================
+ Hits         4865     4868       +3     
+ Misses       1140     1137       -3

Impacted Files	Coverage Δ
...rc/planner/vectorfield/BodyNodePoseVectorField.cpp	66.66% <ø> (ø)	⬆️
include/aikido/planner/vectorfield/VectorField.hpp	100% <ø> (ø)	⬆️
...do/planner/vectorfield/BodyNodePoseVectorField.hpp	100% <ø> (ø)	⬆️
src/planner/vectorfield/VectorFieldPlanner.cpp	75% <100%> (+5%)	⬆️
...anner/vectorfield/detail/VectorFieldIntegrator.cpp	95.08% <100%> (ø)	⬆️