VMR packages should publish to the RepoOrigin's channel respective feed

[ViktorHofer]

Today, a VMR build publishes non-shipping packages to the dotnet10-transport feed and shipping packages to the dotnet10 feed. This includes i.e. Arcade packages which users expect to go into dotnet-eng, System.CommandLine packages which go to dotnet-tools, etc.

We should consider adding functionality to the publishing to determine the feed for each asset in the merged manifest instead of using VMR's feed.

https://github.com/dotnet/scenario-tests/pull/213#issuecomment-2678325732 is an example where this led to confusion and required adding additional feeds to a repository's NuGet.config.