Re-namespace and rename packages about data.hashfunction

[brandondahler]

One interesting thought would be to put the implementations inside a general namespace, such as OpenSource.Data.HashFunction, while putting the package under a "BrandonDahler.Data.HashFunction" prefix. This would better allow individuals to fork the repository and roll their own versions, while maintaining consistency of assembly naming and namespace referencing.

In particular, this could help individuals who want to package and deploy a private version of the code inside their own personal repository without worrying about ambiguous package identities (for instance if they release a soon to be merged PR as its own version internally).

[brandondahler]

Meh, after sleeping on this I'm not feeling that idea a whole lot -- I should probably stick with OpenSource.Data.HashFunction for the package name and if someone wanted to fork they can have a non-canonical package name. If I wanted to be nice to that end, I can make it so that the prefix can be changed in a single directory msbuild file instead of forcing them to change it in 13+ different files.