Cleanup composer.json

The version tag is not required since the branch is named like 1.0 it will automatically receive the 1.0.x-dev treatment by Composer.

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.

---

This goes with the other set of PR's. We can talk more about which direction you'd like to go. I'd suggest moving this branch to be the default branch for people who visit this project if this is going to be the current working branch for this project. Would be the lowest impact thing to do to get this squared away.