Service-def update does not preserve the order in which permissions are listed

Consider a Hive policy - the policy UI lists the permissions in the following order: select, update, create, drop, alter, index, lock, all.

After an update to Hive service-def (for example to add a custom-condition), the policy UI lists the permission in a different order.

For a better user experience and consistency, service-def updates should preserve the ordering of the permissions.