feat: normalize capture-area geometry TDE-1359

[paulfouquet]

Motivation

When an existing capture-area geometry is being modified (polygon being removed/added), as a result the polygons points can be moved around. When the overall geometry ends up being the same (no visual change), we prefer the capture-area geometry to not show a change (difference between existing and new/re-processed one).

Modifications

• Use shapely.normalize() to keep the geometry consistent.

What does shapely.normalize()?

According to the official documentation:

• the coordinates of exterior rings follow a clockwise orientation and interior rings have a counter-clockwise orientation
• the starting point of rings is lower left
• elements in collections are ordered by geometry type: by descending dimension and multi-types first (MultiPolygon, Polygon, MultiLineString, LineString, MultiPoint, Point). Multiple elements from the same type are ordered from right to left and from top to bottom.

Because, "the coordinates of exterior rings follow a clockwise orientation and interior rings have a counter-clockwise orientation" is going against RFC 7946 - "A linear ring MUST follow the right-hand rule with respect to the area it bounds, i.e., exterior rings are counterclockwise, and holes are clockwise.", we need to apply orient() after normalize() the geometry.

Verification

• Unit tests
• Other tests to come in feat: update existing Collection TDE-1359 #1224