Generate packages for e2e tests by using existing ArtifactsShippingPackagesDir

[YuliiaKovalova]

Fixes ##11090

Context

E2E tests for BuildCheck require to have set of MSBuild nuget packages to run.
To avoid having a race condition on the build machines, we agreed to use the existing package generation approach locally too, so no additional logic required.

[JanKrivanek]

Just curious - what is the extra time added to a local dev build when performing incremental build with a single change in one of our projects?

Just trying to see if this is something no worth of any extra thoughts, or if we should try to think about a way how to still keep inner loop quick (e.g. keep the previous approach, while condition on some extra thing passed in CI/official build, that would force skipping the packing in preparation of test assets)

[YuliiaKovalova]

Just curious - what is the extra time added to a local dev build when performing incremental build with a single change in one of our projects?

Just trying to see if this is something no worth of any extra thoughts, or if we should try to think about a way how to still keep inner loop quick (e.g. keep the previous approach, while condition on some extra thing passed in CI/official build, that would force skipping the packing in preparation of test assets)

I haven't noticed any significant wall clock time changes on my device.