Refactoring dependency version resolution in AssemblyAnalyzer

[nhumblot]

Context

Dependency version resolution in AssemblyAnalyzer posses a lot of conditional branches, making the intention of the code harder to understand. The goal of this issue is to isolate this logic and improve the naming and ease the understanding of the intended logic put into this version resolution.

Acceptance criteria

• full coverage of the logic is put under test harness before refactoring
• the dependency version resolution of AbstractFileTypeAnalyzer is isolated and posses clearer naming stating the intention of the code