Ports 0.2 redesign

[Yohe-Am]

• Move away from asdf based download/install/list model
• Ports will be composed of
  • Resolver: function that'll change the user provided InstallConfig into one that the port can work with
    • Entry point for fuzzy version matching
    • Can resolve other non-version fields (rust targets and components for example)
  • Builder: any number of steps to complete that'll produce the final artifacts.
    • We don't really need an install step as ports are not allowed touch user's system. This might prove a blocker for some kinds of software.
    • Each step will be memoized
      • Think incremental computation.
    • This should provide flexibility for ports that need to more than fetch artifacts from network.
    • Implementation should have in mind shape of any future Build module weather we write our own or integrate from third-parties.
    • For the 0.2 impl, just simply adapt the InstallsDb to support more than install/download step.
    • If not possible to do hashing on steps themselves, we can always do hash(port-semver, step-idx)

Early sketch: #36 (comment)

[linear]

MET-412 Ports 0.2