add test cases

[luizbarboza]

• Difference fails with "Unable to complete output ring starting at" mfogel/polygon-clipping#75
• Another union ring problem :) - Unable to complete output ring starting at .... mfogel/polygon-clipping#83
• Union is incomplete mfogel/polygon-clipping#86
• Difference fails with "Unable to complete output ring starting at" mfogel/polygon-clipping#90
• "Unable to complete output ring staring at" mfogel/polygon-clipping#91
• Regression 0.14.3 vs 0.14.2  mfogel/polygon-clipping#93
• intersection output missing a sub polygon mfogel/polygon-clipping#94
• Infinite looping for /* Pass the sweep line over those endpoints */ loop in operation.js  mfogel/polygon-clipping#95
• "Unable to find segment" errors for union op in v0.14.3 and master branch, with integer coordinates. mfogel/polygon-clipping#96
• 'Unable to find segment' on 0.14.3 mfogel/polygon-clipping#98
• Unable to complete output ring starting at ... mfogel/polygon-clipping#101
• union fails with Unable to complete output ring starting at (another case) mfogel/polygon-clipping#105
• Maximum call stack size exceeded mfogel/polygon-clipping#111
• Unable to find segment #13 [35.188333, 6.664167] -> [35.189483, 6.665317] in SweepLine tree. mfogel/polygon-clipping#115
• Error: Unable to pop() right SweepEvent [19.9284281536379, 50.05417333008677] from segment #208 [19.928343489142087, 50.054282582583205] -> [19.9284281536379, 50.05417333008677] from queue. Please file a bug report. mfogel/polygon-clipping#118
• Error: Unable to find segment on difference mfogel/polygon-clipping#122
• Maximum call stack size exceeded on intersection mfogel/polygon-clipping#124
• bug for splay tree remove mfogel/polygon-clipping#129
• Error: Unable to complete output ring mfogel/polygon-clipping#139
• Unable to complete output ring starting at [...]. Last matching segment found ends at [...]. mfogel/polygon-clipping#140
• Error: Unable to complete output ring when subtracting polygons with collinear edges mfogel/polygon-clipping#141
• Error on difference - likely due to overlapping segments mfogel/polygon-clipping#142

[Peque]

@SBanksX Did you run any performance tests after fixing all those floating point issues? I'd be interested in knowing how this implementation compares to https://github.com/mfogel/polygon-clipping.

Of course I can run the tests myself, but I am guessing there is a high chance you run them already while or after implementing the changes. 😊

[markstos]

@Peque Many of the tests come from the polygon-clipping library, which crashes on the test cases, so it doesn't matter if polygon-clipping is faster if it doesn't work.