EPIC: Evolve WIKI into a structured reference doc to cope with requirements of professional workshops

[mi-hol]

• remove obsolete content
  • example: Debug-Mode (see https://github.com/rusefi/rusefi/issues/3614#issuecomment-1354347339)
• structure content along a "red line to follow"
  • good example: https://speeduino.com/Speeduino_manual.pdf

[rusefillc]

Yes please!

[mi-hol]

Plan is to use Dev-Status.md as the table-of-contents (TOC) for rusEFI features

[mi-hol]

Current understanding:

1. improvement requires restructuring wiki content to avoid duplication
2. restructuring is blocked by links in old forum post
3. analyzing links in forum is blocked by lacking progress in https://github.com/rusefi/rusefi_documentation/issues/423

CATCH22

[rusefillc]

2. restructuring is blocked by links in old forum post

let's drop this requirement. let's ignore forum links for sake of documentation progress

[mi-hol]

wont be feasible