Fix incorrect check for Intersecting curves when computing Voronoi regions

[IsakNaslundBh]

Issues addressed by this PR

Closes #95

Check if intersection point is end point was checked against the first curve twice instead of first first curve and then second curve.

Test files

https://burohappold.sharepoint.com/:f:/s/BHoM/EiEigBBMZAJLkDZiU-TpjAEBTh0GOEb43ZdmC_SENq25pA?e=yQ9di1

Changelog

Additional comments

[IsakNaslundBh]

@BHoMBot check unit-tests

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check unit-tests

[IsakNaslundBh]

@BHoMBot check unit-tests

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check unit-tests

[IsakNaslundBh]

@BHoMBot check compliance

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance

[JosefTaylor]

Looking at the test script, the original branch did some funny stuff:

and this is resolved with the fix.

[IsakNaslundBh]

@BHoMBot check required

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check code-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check documentation-compliance has already been run previously and recorded as a successful check. This check has not been run again at this time.

[IsakNaslundBh]

@BHoMBot check ready-to-merge

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check ready-to-merge

There are 9 requests in the queue ahead of you.