A few metadata-mgmt app fixes

[paterczm]

Addresses 3 issues:

• Version dropdown not updated when creating new schema #76
• When data changes via metadata app are successful, the popup makes me think something went wrong #75
• Sort entity names and versions in dropdowns (metadata mgmt app) #72

Note that version sorting is done alphabetically, i.e. 0.10 will come before 0.2. It's not perfect, but hopefully sufficient.

There are no tests. See #79.

[coveralls]

Coverage remained the same at 22.22% when pulling fad6aa6 on paterczm:todos into 74ae58c on lightblue-platform:master.

[coveralls]

Coverage remained the same at 22.22% when pulling fad6aa6 on paterczm:todos into 74ae58c on lightblue-platform:master.

[dcrissman]

Is there any way I could test these changes before approving?

[dcrissman]

@paterczm you will need to merge in changes from master

[coveralls]

Coverage remained the same at 22.22% when pulling aee291c on paterczm:todos into 04f9e56 on lightblue-platform:master.

[paterczm]

Openjdk7 build got stalled twice in a row. But openjdk8 passed - good enough?

[dcrissman]

@paterczm looks like this PR needs a master merge.

[coveralls]

Coverage remained the same at 17.39% when pulling 71814fa on paterczm:todos into 95fd53a on lightblue-platform:master.