[feat]: detect when service needs to be updated in order to meet dependency that has been udpated

[chrisguida]

Currently when you update, eg, bitcoind, but you still have an old version of proxy that isn't compatible with the new version of bitcoind, proxy has a dependency error which recommends downgrading bitcoind rather than upgrading proxy to the new version. The marketplace should detect this scenario and recommend an upgrade of the selected service (proxy, in this example) rather than recommending a downgrade of the dependency (bitcoind in this example).

[ProofOfKeags]

Currently the logic assumes as axiom that the current version of the viewed service is pinned. I think removing this assumption during the computation of suggestions for actions that will rectify dependency errors we should account for new releases to the marketplace from which the package originally came. Further, when both a downgrade or an upgrade would fix the dependency error, we should bias towards recommending the upgrade.

[chrisguida]

I concur