Tutorial helper scripts

[LevFendi]

Adding scripts for making it easier to edit the tutorial files:

1. Updated tutorial-to-markdown script
2. Added tutorial step numbering cleanup script. Needs testing.
3. Will add markdown-to-tutorial script.

The PR also includes changes to the tutorial structure:

1. Chapters will be 99 steps long with step 0 being the title. Unused steps will be empty.
2. The tutorial reader will skip empty steps.
3. There will be a single info box at the top to explain how to make edits and use the scripts.

[ahicks92]

I still think longterm we should maintain the tutorial in markdown, but for now why not. It does solve the problem.

Note that this is actually any Python 3.6 or greater because of the format strings.

Usually you want to do two things: start a script with #! /usr/bin/env python3 and chmod +x. This makes it "just work" on anything except Windows. On windows chmod is trickier: use git update-index --chmod=+x (which I a,ways have to look up, to be fair).

That said I don't really care and if it ever comes to matter I can just do it for you later. The place it could matter is whenever we double down more on CI.

Consider this approved or whatever, I just spotted it and it seemed worth dropping in. I haven't validated the script changes; I'm assuming that you tested, they work, and we'll find bugs later.

[LevFendi]

Added description to explain the intent for this draft PR.

[ahicks92]

If we have markdown to tutorial aren't the others irrelevant? We'd convert to markdown once, which is basically just some find/replace in vscode, right? Then after that we'd just always go md->cfg and the other scripts become useless?

Might as well only maintain one if we can. I'd suggest scoping this such that the conversion happens in this PR< this PR lands as a deleter of the other scripts, and we can just not bother being super paranoid/etc about the new ones because there'd only be the one to review.

[LevFendi]

I suppose that markdown editing will be unequivocally easier so yes, the end goal might as well be keeping only the markdown to cfg script.

The only place where cfg has an advantage is keeping track of chapter lengths to see if you crossed 99. I suppose one can quickly open and close the cfg to check that.

Therefore yeah, when the third script is good to go we can remove the other two or at least not advertise them.

[ahicks92]

Well as I've said before if that genuinely becomes a problem (it won't, 99 markdown paragraphs is a whole novella) then we can query that from the cfg I am reasonably sure.

I kind of care which way we go, because markdown is easier, but the most important thing is that we have one authoritative copy.

My idea for markdown is heading levels for chapters and steps and then paragraphs under those. Bit tricky to parse without a library. There are libraries, but I only know the Rust landscape.

[LevFendi]

I agree on the headings and paragraphs, as that is already what we do in the tutorial transcript.