organize test based on dependencies

[LaszloGombos]

The main motivation is to organize test based on dependencies, so that when test fail/regress on the CI, it is easier to troubleshoot.

Proposal:

• 10-29: systemd and networking optional
• 30-59: systemd required, networking optional
• 60-89: networking required, systemd optional

To minimize the number of changes, here are the mapping of old and new test numbers. Numbers not listed would not changed (e.g. tests 10-17)

old -> new

• 01 -> 20
• 02 -> 30
• 03 -> 21
• 04 -> 31
• 20 -> 60
• 30 -> 61
• 35 -> 62
• 40 -> 63
• 50 -> 64
• 60 -> 65
• 62 -> 19
• 63 -> 20
• 98 -> 21

We should make this change when there are no active development on tests and CI.

[LaszloGombos]

CC @bdrung

[bdrung]

The proposal looks good. Maybe add a section for dracut-live and one for dracut-squash.