More inlining... I don't understand the need for a version number that is managed by the
engine. I think a client may use whatever version scheme they use. We just need to validate that the version identifier is unique at deployment time.
It's always nice to have a default behaviour. So we can have an easy 80% of cases where you just redeploy the same process and don't care what its versio number will be.
