Better macro architecture

[sezanzeb]

• The available arguments of macro functions (now called Tasks) are now very clearly defined, instead of using function-inspection and parameter-name conversions to do this stuff
• Each task has its own class. They can be extended in there without cluttering the Macro object anymore. There is space for more complex macros
• Task classes are very easy to understand now I think. New macros are easier to write.
• It uses the same class for both constant (KEY_A and stuff) and variable arguments ($foo), instead of wrapping the latter, while leaving the first one raw.

The new architecture is certainly bulkier than the old one with all the new classes, but I think it's worth it. New classes are: Task, Argument, ArgumentConfig, RawValue. Variable has been extended.

Renamed MacroParsingError to MacroError because this stuff is also flying around during runtime.

[github-actions]

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

mypy

---

[mypy] _{reported by reviewdog 🐶}
error: Argument 3 to "Task" has incompatible type "Context | None"; expected "Context" [arg-type]

input-remapper/inputremapper/injection/macros/parse.py

Line 362 in 53f8b9f

context,

[sezanzeb]

@jonasBoss no hard feelings if you are busy with other stuff. Maybe I could just merge this and the other PRs (#1004 and #1007) slowly one by one, and maybe in the future, if you feel like it, make a review and I'll fix any comments in a new PR.