Detecting dependency version conflicts

[bvssvni]

When a breaking change occurs in the libraries listed in the extraction info, all dependency version conflicts can be solved by upgrading to the newest version, see #16.

When a library is not listed in the extraction info, a dependency version conflict might occur. I believe the right way to solve this is to use the newest version used by any dependency, because:

1. Given a localized part of the ecosystem, a downstream library depending on that part should not experience dependency version conflict after the information from Eco is used to upgrade the libraries.
2. Dependency version conflicts are caused by multiple dependency paths to different versions of the same library. This is possible when a subset of the localized ecosystem contain different versions of the same library.
3. It is not possible to prevent a downstream library from using a subset such that a dependency conflict does not occur.

Also, a localized part of the ecosystem might use an older version of a library to speed up development for a time period. In this case it is desirable to have the easiest upgrade possible.

The only solution that satisfy these constraints is by upgrading to the newest version used by any dependency.

• For all libraries not listed in the extraction info, find the newest version
• Add an update action for versions of the same library that uses an older version

[bvssvni]

Done.