Reorganize build output (bin) directories

[CharliePoole]

Currently we build into a set of bin directories according to the target runtime... net20, netcoreapp3.1, etc. Then we Publish the projects into the same directories. This can be very confusing to debug because it's not always obvious whether a problem has arisen in the build step or the publish step.

Since we do now publish all the binaries to BIN_DIR, I'm proposing that we go back to the naive build approach of having a bin directory under each project. We can then continue to publish them to the main bin directory (BIN_DIR) and that published structure does not have to match the existing one. Rather it can be made to look pretty much like the structure we want in our packages allowing further simplification.

@rprouse @mikkelbu @jnm2 I'd appreciate comments on this idea before I do it.

[mikkelbu]

Given the confusion in #1044 I think it is fine to separate them

[CharliePoole]

Changes in the 3.15.0 release have simplified the publishing step substantially. I'm moving this to 4.0 for further investigation.

[CharliePoole]

This issue has been resolved in version 3.16.0

The release is available on: GitHub. NuGet packages are also available NuGet.org and Chocolatey Packages may be found at Chocolatey.org