Enable dependency flow

[chcosta]

Dependencies which are a part of source build, but do not publish using dependency flow end up causing incoherent builds. Source build is not able to determine which version of the asset is needed because it is not reported to BAR and then someone must manually go to a repo (like core-sdk) and trace back to find which version of the dependency is needed so that it can be built.

https://github.com/dotnet/arcade/blob/master/Documentation/DependencyFlowOnboardingWithoutArcade.md

[singhsarab]

/cc: @cltshivash @PBoraMSFT We would need to plan this work.

[chcosta]

Any update on this?

[singhsarab]

@chcosta This work is planned for this quarter. Will update once, we pick this.

[chcosta]

@singhsarab , am I to take "this quarter" as meaning, "it will be done by June"? The last day for .NET Core 3.0 support in Jenkins is May 3rd.

[singhsarab]

@chcosta How is this related to Jenkins ?

[chcosta]

Ack, you're right, my bad. I crossed streams.

[singhsarab]

@chcosta fixed the issue hit while trying to generate manifest. Refer dotnet/arcade#3080 (review)