feat(map_generation): use aruco markers on sketch map

[matthiasschaub]

This PR consists of 4 parts:

1. build(dep): fix opencv version to work w/ ultralytics and update ruff version
2. test(approval): add image reporter and approver, add NDArray Reporter/Approver and add pytest namer factory
3. refactor(map_generation): rename canv to canvas
4. feat(map_generation): use aruco markers on sketch map

It might be useful to review this PR commit by commit.

For now aruco markers instead of globes on Sketch Maps are optional. This feature flag is enabled by giving a query parameter aruco=true to the /create endpoint (e.g. http://localhost:8081/en/create/aruco=true).

The advantage of Aruco markers might be:

1. Every Aruco marker is unique (in contrast to the globes).
2. Aruco markers can be used in clipping the map frame from uploaded sketch maps using as it is done currently using BRSIK or a marking detection algorithm provided by opencv2 in the future. Initial experiments using the latter algorithm were not promising. This PR continues to use BRSIK regardless of marker types.

This PR does adress in parts #488 and #502

Todo:

• update production database table map_frames to include attribute aruco defaulting to FALSE
  -> Executed on the production database:

ALTER TABLE map_frame
ADD aruco BOOLEAN DEFAULT FALSE;

[itisacloud]

I would maybe propose to use more complex Aruco markers in fututre in comparison to the 4x4 grid, as brisk relies on texture, and an 7x7 grid could be lead to a higher rate of succefull clippings. I will include this as a parameter in my future perfomance testing.

[matthiasschaub]

@itisacloud interesting, because the algorithm for detecting aruco markers from opencv works best if the markers are less complex. But its of course not in use at the moment.

I am going to merge it, but feel free to change it if your testing found that it works better with complex markers. Or should this maybe be configurable?;

Thank you for taking the time to review the PR!