Update the Wizard school to new standards

[tsathoqqua]

Update all files under
https://github.com/limalib/lima/tree/master/lib/domains/std/school

[azerwyn]

Some style questions:

1. Is the include style in school.h considered best practice? or even recommended? As an example, it is painfully abbreviated. When a standard of preprocessor expectations is applied top down, it can be helpful; such as, when it comes time to move stuff around; however, when every dev takes it upon themselves to use their own personal style of preprocessor-fu, it can get, frustrating. Probably not as much a problem today as it was 20 years ago -- not so many fingers in the pie.

Is this something that should simply be in the "opinionated" basket? like indents? Or is there a "reasonable person" standard that might apply?

2. Is the string processing method @FOO text FOO still considered appropriate with the move toward wider displays and other string processing features? I agree there are use cases for specialized displays where precision placement is necessary, ala maps or ascii imagery. For general text descriptions and such, I lean away from it because @TEXT TEXT can interfere with the desired top-down look and feel (or limit creative programmatic descriptions). I suppose this might fall into the category of "they who put in the effort lead by example".

I'm not trying to be controversial or contentious, just curious where the wind is blowing before looking too deeply into this.

[tsathoqqua]

1. That include style is both horrible and not recommended. The reasons to avoid this is partly described here: https://docs.limalib.dev/domain_dev/dom_create.html#domain-defines
2. It can be okay, I strongly prefer not using those, and would like the wizard school rewritten without using this style. I have yet to find a mode for Visual Studio Code that can actually handle this syntax properly. And losing ability to automatically indent an entire buffer of C code just to keep the @foo syntax is not worth it.

[azerwyn]

Just and update.

1. The discussion on the parsing of fancy_long() and the overload solution has removed a frustration with converting or preserving the useful content.
2. I got distracted with an idea to create some form of registration, progress tracking, testing, and stage gate awards. I stopped scope creeping when I realized I was beginning to abstract the "terminal" functions into modules and actions. I'll do that another time. I want to refocus on getting something updated/workable/useful first. Improvements can always come later.