Fix Flying Edges z-boundary condition with non-square input (Version 1.7)

There was a bug with Flying Edges checking the boundary conditions in the z-direction. It was comparing the z index to the size of the y dimension, not the z dimension. This simple typo was probably missed because most of the tests use square meshes. To catch the problem, you need a mesh that has a different number of points in the y and z directions and the contour has to go past the positive z boundary.

When this error was hit, the indices for the edges on that boundary were not recorded, and later interpolation used garbage values for edge's point ids.

This MR applies the fix for #727 (closed) (as available in !2875 (merged)) to the version 1.7 release branch.

requested review from @vbolea

This merge request has been queued for testing. Test results may be viewed on:

• Gitlab CI builders results can be viewed via the Pipelines for this merge request.
• CDash links are also available in the Pipelines page
• CDash (release-1.7)
• Buildbot (release-1.7) (only visible from inside Kitware)

Branch-at-release-1.7: a195ce88

+1 CI passing

ping @kmorel

Whoops. I must have forgot about this while waiting for the CI.

Do: merge

Errors:

• While processing the merge command: refusing to merge; topic is missing the checks

Do: check

Warnings:

• Eligible for the 1.9.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

Do: merge

mentioned in commit ca39bd4e

merged

mentioned in merge request !2889 (merged)