Cleanup composer.json for 0.0.x-dev

Removed 0.0.1-beta1 version as it was not actually doing anything. Added a branch alias that will enable people to require:

    "ircmaxell/security-lib": "0.0.*@dev"

An unintended side effect of composer.json changes is that it results in composer.lock needing to change to account for a different hash. In addition, Composer sometimes actually changes other aspects of the composer.lock
structure.

---

I'll be sending another PR to cleanup composer.json for v1.0 branch.

If the v1.0 branch is going to be the primary branch going forward (since it looks slightly newer) it might make sense to either change the default branch on githup to be v1.0 instead of master or else rename:

 * master -> 0.0
 * v1.0 -> master

The latter seems to be what a lot of people do, but I think it is up to personal taste. It is, however, difficult to figure out what is going on as it stands currently. master is actually, as far as I can tell, older code... and that is what I get shown when I first visit the github page.