feat(qualification): adding resolving version from nns via rollout dashboard

[NikolaMilosa]

This PR addresses a long known issue of qualifying from wrong versions.

The issue (as explained by David Derler):

The issue I’m referring to is the following.
mainnet_revisions.json is updated when the NNS is updated to version v1. This happens on day X (e.g. Monday).

• On day X - k (say Thursday of the previous week) we, most likely already have a qualified v2
• On day X + l (say Thursday of the week following the rollout of v1 ) we qualify another release v3.
• On day X + m (say Monday of the following week) v2 hits the NNS.
• After that v3 rollout starts and will hit the NNS on day X + m + 7.
  So the issue is that the qualification test runs between v1 <-> v3 as opposed to v2 <-> v3.
  The fix might be as easy as testing against the version of io67a in the mainnet_revisions.json and make sure that the qualification only runs once io76a has v2

It uses newly developed rollout dashboard.

NOTE: this only solves one issue and ensures that the version that will run on NNS (as forecasted by rollout dashboard) will be upgradable to the new version (being qualified in qualification process).

One more issue that needs tackling is the possibility of multiple different versions on the network where each subnet can be on different version when the rollout finishes. This issue will be addressed soon after this change is integrated.