Semantic Versioning

Ensure that people can start requiring "ircmaxell/random-lib" using semantic versioning like the following instead of forcing people to use `dev-master` as the version:

    "ircmaxell/random-lib": "1.*@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.

---

Somewhat related, I'm going to follow up on security-lib and see how/why `dev-master` is required there. I see there is 1.0.x-dev branch but also dev-master. I'm not sure if dev-master is newer? Or older? How does it relate to 1.0.x-dev? I'm going to guess that dev-master is actually supposed to mean something like 1.1.x-dev?

If master should be considered something like 1.1.x-dev I'll do something similar to what I'm doing here (adding a branch alias for dev-master => 1.1.x-dev) to get us to the point where we can require `1.1.*@dev` instead of `dev-master`. Then I'll make that change against RandomLib's composer.json.

If this sounds like a good plan to you, you can merge this now and then I can send another PR after we've worked through security-lib to require the new dev version instead of `dev-master`. Or if you prefer, you can just hold off on this PR and I can update it after we've handled the SecurityLib changes. I'm happy to go down either path. :) Just let me know how you'd like to move forward.