Since EZP-20750 ordering of versionInfo is done by SPI layer, and thus the ordering done in PHP in ContentService is no longer needed. So this is about documenting that behaviour on SPI to be 1. able to refactor away the sorting code in ContentService and 2. be prepared for possible paging support on this API point in the future (which can only work properly if sorting is done in persistence layer).