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-2.0.1/patches/posixmodule.patch

@@ -1,33 +0,0 @@
-SPDX-FileCopyrightText: 2022 fosslinux <fosslinux@aussies.space>
-
-SPDX-License-Identifier: Python-2.0.1
-
-musl (correctly) implements the POSIX posix_close function, however
-this was added well after Python 2.0.1 was released.
-
---- Modules/posixmodule.c	2022-09-16 16:46:09.809812072 +1000
-+++ Modules/posixmodule.c	2022-09-16 16:47:23.254166370 +1000
-@@ -3267,12 +3267,12 @@
- }
- 
- 
--static char posix_close__doc__[] =
-+static char py_posix_close__doc__[] =
- "close(fd) -> None\n\
- Close a file descriptor (for low level IO).";
- 
- static PyObject *
--posix_close(PyObject *self, PyObject *args)
-+py_posix_close(PyObject *self, PyObject *args)
- {
- 	int fd, res;
- 	if (!PyArg_ParseTuple(args, "i:close", &fd))
-@@ -5300,7 +5300,7 @@
- 	{"tcsetpgrp",	posix_tcsetpgrp, METH_VARARGS, posix_tcsetpgrp__doc__},
- #endif /* HAVE_TCSETPGRP */
- 	{"open",	posix_open, METH_VARARGS, posix_open__doc__},
--	{"close",	posix_close, METH_VARARGS, posix_close__doc__},
-+	{"close",	py_posix_close, METH_VARARGS, py_posix_close__doc__},
- 	{"dup",		posix_dup, METH_VARARGS, posix_dup__doc__},
- 	{"dup2",	posix_dup2, METH_VARARGS, posix_dup2__doc__},
- 	{"lseek",	posix_lseek, METH_VARARGS, posix_lseek__doc__},