Consume project-specific PackageVersions.props file in end tarball build

[oleksandr-didyk]

Part of #2482

Given all tarball-contributing repositories being able to produce PackageVersions.props file (#3043), the tarbal should be able to consume the individual files instead of the current logic of building the same file but for all projects combined.

Afterwards, a SB tarbal with the functionality would be produced and tested against to verify the changes made before making repo PvP the default behavior

[oleksandr-didyk]

Expected implementation time -> 5-7 working days

[MichaelSimons]

Before this work starts in the tarball, this feature should be picked up by each individual repo contributing to the tarball build. Repos should opt in initially and once all onboarded the functionality should be on by default.

[oleksandr-didyk]

Before this work starts in the tarball, this feature should be picked up by each individual repo contributing to the tarball build. Repos should opt in initially and once all onboarded the functionality should be on by default.

My bad, initially forgot about this, will edit the description

[oleksandr-didyk]

Edited the issue description to properly reflect the pre-requisite for the task

[MichaelSimons]

This is not needed. There will still be a single versions.props for everything in the source-built archive. A PackageVersions..Previous.props is generated at build time for each repo to pull in only the properties from source-build dependencies within the Version.Details.xml/