DI Compile - Sort DI metadata output to make diff between builds easier

[andrey-legayev]

Description (*)

We've faced an issue on BitBucket Pipelines: every build had own unique order of keys inside DI Metadata files.
We couldn't see the real diff between builds because of it.
Simple alphabetical sorting of metadata keys resolves this issue and makes builds repeatable.

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

1. Run DI compile on base branch then copy folder "generated/" to "generated-old/"
2. Run DI compile on this branch then copy folder "generated/" to "generated-new/"
3. Compare folders. You should not see diff in metadata.

Questions or comments

N/A

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @andrey-legayev. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-6038 has been created to process this Pull Request

[engcom-Alfa]

✔️ QA Passed

[m2-assistant]

Hi @andrey-legayev, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

[VladimirZaets]

Covered by magento2ce/setup/src/Magento/Setup/Test/Unit/Module/Di/Compiler/Config/ReaderTest.php test