Remove the notion of "sys*"

- This idea originates from very early in the project and was, at the
  time, a very easy way to categorise things.
- Now, it doesn't really make much sense - it is fairly arbitary, often
  occuring when there is a change in kernel, but not from builder-hex0
  to fiwix, and sysb is in reality completely unnecessary.
- In short, the sys* stuff is a bit of a mess that makes the project
  more difficult to understand.
- This puts everything down into one folder and has a manifest file that
  is used to generate the build scripts on the fly rather than using
  coded scripts.
- This is created in the "seed" stage.

stage0-posix -- (calls) --> seed -- (generates) --> main steps

Alongside this change there are a variety of other smaller fixups to the
general structure of the live-bootstrap rootfs.

- Creating a rootfs has become much simpler and is defined as code in
  go.sh. The new structure, for an about-to-be booted system, is

/
-- /steps (direct copy of steps/)
-- /distfiles (direct copy of distfiles/)
-- all files from seed/*
-- all files from seed/stage0-posix/*

- There is no longer such a thing as /usr/include/musl, this didn't
  really make any sense, as musl is the final libc used. Rather, to
  separate musl and mes, we have /usr/include/mes, which is much easier
  to work with.
- This also makes mes easier to blow away later.
- A few things that weren't properly in packages have been changed;
  checksum-transcriber, simple-patch, kexec-fiwix have all been given
  fully qualified package names.
- Highly breaking change, scripts now exist in their package directory
  but NOT WITH THE packagename.sh. Rather, they use pass1.sh, pass2.sh,
  etc. This avoids manual definition of passes.
  - Ditto with patches; default directory is patches, but then any patch
    series specific to a pass are named patches-passX.

sysc/python-3.8.16/patches/maxgroups.patch

@@ -1,20 +0,0 @@
-SPDX-FileCopyrightText: 2022 fosslinux <fosslinux@aussies.space>
-
-SPDX-License-Identifier: PSF-2.0
-
-MAXGROUPS constant was introduced in this upgrade. Hardcode it
-from a "normal" system. This seems particularly unproblematic
-if it is wrong, since it does next to nothing.
-
---- Lib/sre_constants.py	2022-12-20 12:05:01.176104156 +1100
-+++ Lib/sre_constants.py	2022-12-20 12:05:21.710376396 +1100
-@@ -15,7 +15,8 @@
- 
- MAGIC = 20171005
- 
--from _sre import MAXREPEAT, MAXGROUPS
-+from _sre import MAXREPEAT
-+MAXGROUPS = 1073741823
- 
- # SRE standard exception (access as sre.error)
- # should this really be here?