Edge direction in getH3UnidirectionalEdgeBoundary is inconsistent

[nrabinowitz]

This may not be a big deal for most consumers, but the algorithm used for getH3UnidirectionalEdgeBoundary produces 5 edges that follow the direction of the origin's geo boundary output, and one edge that goes in the opposite direction (from the origin's vertex 5 to vertex 0).

Given that we might rewrite that algorithm to something more efficient in any case, it would be a useful requirement for the output that all edges follow consistent directionality.

[nrabinowitz]

Oh, rats. The same issue also results in the wrong order if the last-to-first edge is distorted and has three vertices - on a 10-vertex pentagon, the last edge has the vertexes in order [0, 8, 9], which is incorrect.