instead of only placing markers for points.

The code that manages a ol/Layer/Vector has been moved from the marker component to a composable, so that it can be used by the component that will highlight features.

as it will then be used in the highlighting of feature to lookup for the most southern feature of the selected

it will be used in both cases, and this way we do not have to declare a third type of selectable features (GeometryFeature or something in this vein), most of the code will stay the same whilst supporting selection of geometry

keeping all features visible in the process. The rotation of the map is rarely not pointing north, so I though it wasn't making much sense to take the rotation of the map into account while calculating this point, but that could easily be achieved by computing the point we give to the nearestPoint function, and moving it according to the map rotation

We return a LayerFeature instead of the specialized one for drawing, making our feature identification compatible with external KML in the process.

Also changing how the popup for KML feature is built, and using the layer title (common practice between layers) and trying to find a description for this specific feature. If no description is given, fallback to a "no further information" text instead of leaving the popup empty.

All features from all years were requested, with this new param only the selected year's features will be returned

so that only const and let keyword are permitted

also fixing an issue with drawing and the way we now select the popover coordinate, passing the drawn geometry directly into the feature (even when drawing, before it was using the coordinates directly without knowing what kind of geometry it was dealing with)

so that they are present to place the popover when we click on a feature while drawing

We didn't detect that there was issues with the popover placement because tests are only performed with a mobile viewport, meaning the popup is placed in the infobox at the bottom of the screen, without the computation for a over-the-map placement (where the issue was located)

So I've added a test that toggles the floating of the edit popup for a marker and a line (as the calculation is a bit different for these two types when floating)