Organizing build output into separate folders

In the DevOps way of working, teams are encouraged to adopt the right tools and practices earlier in the development lifecycle to minimize waste later. While the pre-canned build templates make it really easy to get started with build pipelines, the generic configuration bloats the build artifact and adds folders that you don't necessarily care about. The ones that you do care about are folded into multiple hierarchies. While it isn't necessarily a problem immediately, when you start to consume the build output in release pipelines, much of the release pipeline effort is spent in organizing the build output correctly. In the spirit of pushing more software development activities left into the lifecycle and minimizing waste, let's see how easy it is to organize the build output into relevant folders from the outset...