Automate the ODL release process

[corranrogue9]

The current release process has a number of manual steps. We should automate them to ensure consistency of releases, avoid easy manual mistakes, to reduce the amount of time it takes to perform a release, and to reduce the amount of developer resources spent on performing a release.

[robertmclaws]

The release consistency problem has little to do with these manual steps, in my experience. Instead of "adding a script", the entire solution needs to be modernized and simplified.

ODL, WebAPI, and OData 8.0 all contain a massive amount of cruft from nearly 2 decades of development.

The projects need to be upgraded to SDK-style projects, Directory.Build.props files need to be used, and modern analyzers should be dropped in instead of FXCop and 90% of the stuff in the tools folder.

To my understanding there is little to no reason why this project should still need such extensive build customizations. It's a simple set of class libraries.

That's one of the first steps we did on the Restier project and it was a massive improvement for manageability. It shouldn't take giant readme and a crapload of scripts to build this project.

I've tried several times to rebuild this solution based on modern techniques, but every time I've stopped because I wasn't sure there was going to be buy-in from the team. I'm happy to help drive the upgrade if I can be sure the PR will be accepted.

[KenitoInc]

Build system issue OData/WebApi#2777