Recommended entry order when linting .shed.yml files

Currently https://galaxy-iuc-standards.readthedocs.io/en/latest/best_practices/shed_yml.html does not specify a recommend order for the `.shed.yml` entries, but we have a convention in the order used for `tools-iuc` (assuming it is consistent).

Should `planemo shed_lint` enforce this (as it does for the Tool XML order)?

Start with the linked shed_yml best-practices page and the existing planemo shed_lint behavior for Tool XML ordering. Compare the .shed.yml entry order used by tools-iuc, then determine the intended convention and whether it should be documented and enforced. Done means the expected order and enforcement scope are settled and covered by tests.

Written by the indexing model from the issue text.