Contour Output Error in X/Y implementations (non CUDA vs CUDA)

Regression tests for the contour filter showed some drastic differences in asymmetrical output run on structured datasets using the flying-edges algorithm in CUDA vs non-CUDA devices.

Using an asymmetrical contour object caused some obvious issues in the Xaxis summation of the flying edges algorithm in comparison to the Yaxis summation.

X-axis implementation (non-cuda):

Y-axis implementation (cuda):

This needs to be address and fixed so that the contour output is the same for both of the flying edges implementations.

Link to full discussion: !2161 (comment 841342)