Maestro sometimes doesn't add darc feeds to nuget.config

[dkurepa]

This is something I've been noticing for a while, and also something our customers reported recently: https://teams.microsoft.com/l/message/19:[email protected]/1731647680149?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4d73664c-9f2f-450d-82a5-c2f02756606d&parentMessageId=1731647680149&teamName=.NET%20Core%20Eng%20Services%20Partners&channelName=First%20Responders&createdTime=1731647680149.

Basically, when we're flowing stabilized packages through Maestro, sometimes the temporary darc feed containing the package is not added to nuget.config, even tho the build has assets in it. This causes PR failures and needs manual intervention to be resolved

[mmitche]

This is because a new build of the same sha did not get published (typically because it was on a different branch). When two builds have the same sha and same version numbers for a given asset, maestro chooses the newest one. It has no easy way to disambiguate.