Create a "comparer" that will get all the tasks from a matrix and compare them 2 by 2.

For example, when comparing tasks A and B, if A is decided to be more important than B, it will have its importance property increased by 1.

Similarly for urgency. Importance and Urgency are independent, so it's possible that A is set as more important but B is more urgent.

One problem we have here, is that to compare all tasks 2 by 2 may end up in too many comparisons. For instance, if we have 20 cards, that would be the combination of 20 items 2 by 2 which is 20!/(2!)(18!) or 190 comparisons.

One way to reduce this is to consider the comparisons to be transitive, i.e. if A is more important than B, and B is more important than C, then we consider A more important than C and this comparison doesn't have to be made by the user.

The sorter method should be iterative and keep requesting the comparison of 2 cards until all of them have been classified.

Note: To make this work with any number of cards we may have to remove the maximum limit allowed for urgency and importance (currently set from -10 to +10 on Task.MAX_SCALE_VALUE and Task.MIN_SCALE_VALUE respectively.

We should allow a task to have its default urgency and importance set during initilization, for easier use of the class.
Ensure that the values given are validated, maybe using __post_init__ on the dataclass?

We currently calculate a task's "ranking" as the Euclidian distance of the task urgency and importance coordinates in relation to the point of maximum importance and urgency (see prioritization.jpg on the project's root).

That means that the higher the ranking value, the less urgent/imporant is the task.

This is misleading as the convention is that the higher the ranking of a thing, the more "important" it is.

Therefore we will replace the term ranking with priority across the project, as priorities as usually thought as "the lower its number, the more important it is", on a project the most important task is assigned "Priority 1", the second most important "Priority 2" and so on.

Our current diagrams are JPG and they were pushed as files with the code, they should be in a separate repository (github user content)