BugFix: Van der Corput - consider span for resolution check

[aditya-vk]

Expected behavior for VDC with resolution 0.5:

1. If an edge is of length(span) 1, output is 0, 0.5, 1.
2. If the edge is of length(span) 2, output is 0, 0.5, 1.0, 1.5, 2.0.

Current behavior generates sequence for [0,1] and multiplies with length thus giving

1. 0, 0.5, 1.0
2. 0, 1.0, 2.0

We have been using Van der Corput sequence only for interpolated trajectories with [0, 1] time so it was not an issue.

This PR introduces a test that fails with the current master and proposes a fix.

---

Before creating a pull request

• Document new methods and classes
• Format code with make format

Before merging a pull request

• Set version target by selecting a milestone on the right side
• Summarize this change in CHANGELOG.md
• Add unit test(s) for this change

[jslee02]

Good catch! This fixes for the VDC value, but the resolution seems to need to be fixed as well.

Not critical for this PR, but I found a type while reading the header here: Construts --> Constructs

[jslee02]

Why not keeping this test? Isn't this still a valid test?

[aditya-vk]

I figured the replaced test would suffice for both. I brought this back and added a separate test for this bugfix.

[aditya-vk]

@jslee02 fixed both the value as well as the resolution.

[jslee02]

LGTM!

As a note, I still see the type here. Don't need to be fixed by this PR though.