Fix order of hook execution

[gui1117]

Fix #6280
Fix #9105

polkadot companion: paritytech/polkadot#4181
cumulus companion: paritytech/cumulus#711

Breaking Change:

• AllPallets is deprecated in favor of explicit: AllPalletsWithSystem, AllPalletsWithoutSystem, AllPalletsWithSystemReversed, AllPalletsWithoutSystemReversed. Before this PR AllPallets represented all pallets without system in reversed order (i.e. same as AllPalletsWithoutSystemReversed, it now represent AllPalletsWithSystem as it is a more sane expectation.
• frame_executive::Executive requires as generic all pallets with system. Before this PR the type required as generic all pallets without system and always executed system pallet hook before all pallets hook. But this requires duplicate works and error prone implementation thus it now requires all pallets with system. The previous order was to execute the hook on system pallet first and then AllPallets. It is recomended to use one of AllPalletsWithSystem or AllPalletsWithSystemReversed or AllPalletsReversedWithSystemFirst.

Because before the PR all pallets represented all pallets in reversed, and system was executed first then if someone want to keep the same behavior as before they should use the type AllPalletsReversedWithSystemFirst when using the type frame_executive::Executive.
Though it is recommended to be careful about the order of definition of the pallet in construct_runtime. and probably reorganize and use AllPalletsWithSystem, so the order is the expected normal order and not in reversed (as before this PR).

NOTE: frame_executive::Executive will execute the hooks on_initialize, on_idle, on_runtime_upgrade, on_finalize, offchain_worker on the generic AllPallets, so the order should be reviewed for those execution.

Upgrade guide:

1. use AllPalletsReversedWithSystemFirst when instancing executive type, that mean the execution order is not changed from before this PR, thus no need to change anything in construct_runtime.

2. Use the new AllPalletsWithSystem, but this would mean that they might need to reorder some stuff in construct_runtime.

3. review other usage of AllPallets and change to AllPalletsWithoutSystemReversed in case the old order must be kept, or change to AllPalletsWithoutSystem to get the new definition with pallets defined in the order of their declaration in construct_runtime.

[gui1117]

for the polkadot It seems we don't need any changes:
maybe scheduler should be put last instead of 2nd. So that the execution of scheduled call happens after other pallet initialization ?

[shawntabrizi]

I think this is also a noteworthy change. Here system pallet upgrades after the runtime upgrades.

Dunno actually if this can cause issues?

[gui1117]

I think for pre_upgrade/post_upgrade the order wasn't so important as it is just checks.
But the order of on_runtime_upgrade is important. That said the order was: custom, then system then pallets.
I will precise this in the note

[kianenigma]

try_on_runtime_upgrade should always imitate what the real on_runtime_upgrade would do, which is respected here, so no issues.