Make the tutorial steps easier to maintain

[LevFendi]

The problem

The numbering aspect of tutorial steps is currently hardcoded, such that chapter lengths are forced to be exact and it is difficult to add or remove steps from the middle of a chapter, because you have to manually renumber the steps each time. This makes it harder to revise the tutorial and it makes it much more difficult to adapt it for different locales.

The desired solution

Every chapter should be able to have any number of steps, and it should not require much effort to add or remove steps from the middle of a chapter.

A proposed solution

• Extend each chapter to be 100 steps long, but unused steps at the end can be kept empty.
• Reprogram the tutorial module to skip empty steps at the end of a chapter.
• Create a text processing script in python (or another language of your choice) that fixes the step numbering across the tutorial cfg file after changes have been made to it.

Proposed result

• You delete tutorial steps you do not want and you insert as many steps as you want in between existing steps as long as the total count does not exceed 100 per chapter (including step number 0 for the title and 99 for the last step).
• You run the numbering correction script once after you are done.
• For each chapter, the script deletes all empty steps, renumbers all the remaining steps, and then adds empty steps to the end as required.
• The tutorial module reads steps in order and skips the empty steps at chapter ends.

New or remaining problems

• Different locales may have wildly different step counts for the same part of the same chapter. However, this might still be what we prefer so that sentence lengths make sense.

[LevFendi]

This issue is being explored in PR #224. The latest idea (discussed there) is to have only a single markdown-to-cfg script so that all tutorial text editing is done on markdown files.