Previously worked on supposition that all version were synched
(i.e. all aidge modules were on 0.3.xx at the same time).
This is not the case. This led to issue like this releas pipeline
https://gitlab.eclipse.org/eclipse/aidge/aidge_quantization/-/pipelines?page=1&scope=all&ref=v0.2.0
where version retrieved for core & backend cpu were 0.2.xx instead of 0.3.xx

For context check eclipsefdn/helpdesk#5378 (comment 2932378)

now parses tag values to look for latest corresponding tag instead of retrieving tag chronologically

previously retrieved latest tag chronologically, now parses tags to retrieve latest corresponding tag depending on version values

fix : added datetime typing to date sorting for release jobs to ensure date was not treated as a string

This exist for 2 reasons :
- random tests can lead to random unit tests failure
- the following line causes random failure on windows build jobs : https://gitlab.eclipse.org/eclipse/aidge/gitlab_shared_files/-/blob/main/.gitlab/ci/download/download.gitlab-ci.yml?ref_type=heads#L162

This exist for 2 reasons :
- random tests can lead to random unit tests failure
- the following line causes random failure on windows build jobs : https://gitlab.eclipse.org/eclipse/aidge/gitlab_shared_files/-/blob/main/.gitlab/ci/download/download.gitlab-ci.yml?ref_type=heads#L162

onnxruntime
required for MR aidge_onnx!75