Today, we discover which package versions to insert into project's Versions.props files by inspecting all nupkg files in the project's artifacts folder (filtering to the newest version of each asset).

When we move to allowing dev builds, developers can end up in a state where they've done a development build and now all future builds (official or otherwise) only pick up dev builds as they're versioned 42.42.42.42. Additionally, switching between dev branches could end up in a bad state selecting the wrong version of packages.

We already have a known-accurate manifest of all produced assets, the asset manifest. We can extract package versions from the manifest and use that information to update the Versions.props files. Additionally, we can use this same logic to solve #4297 and a similar scenario in the arcade repo project.