TASK: list packages by loading order in BE Module

[crydotsnake]

Upgrade instructions

None

Review instructions

This pull request is related too: https://github.com/neos/flow-development-collection/pull/3363

There we decided to list the packages by their loading order in the flow:package:list command.

This pull request takes care that the packages are listed by the loading order in the backend module too.

Checklist

• [x] Code follows the PSR-2 coding style
• [ ] Tests have been created, run and adjusted as needed
• [ ] The PR is created against the lowest maintained branch
• [ ] Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• [ ] Reviewer - The first section explains the change briefly for change-logs
• [ ] Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[Sebobo]

The module should then show an information about the order.

Btw. I usually prefer alphabetical order as customers tend to show me that list when we discuss updates. Via screenshare the alphabetical order is more useful for me than the loading order.

Probably better to ask the community what they think or if people actually don't care.

Or make it switchable.

[crydotsnake]

Personally i would be fine to sort the package by alphabetical order

Wdyt? @mhsdesign @kitsunet @ahaeslich

[ahaeslich]

If we have use cases where either the alphabetical or loading order is needed, I would go with the option "make it sortable". As in "let the user decide which order is needed now".

If we decide to have this selection in the backend module: how can we be sure the alphabetical order isn't needed by someone in the CLI (see: https://github.com/neos/flow-development-collection/pull/3363)? Is there any need to remove it there?