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.

sysa/tcc-0.9.27/patches/ignore-static-inside-array.patch

@@ -1,59 +0,0 @@
-SPDX-FileCopyrightText: 2018 Petr Skocik <pskocik@gmail.com>
-
-SPDX-License-Identifier: LGPL-2.0-or-later
-
-From ef668aae1ee2b8bc904c50a13bf58df613b2f0b0 Mon Sep 17 00:00:00 2001
-From: Petr Skocik <pskocik@gmail.com>
-Date: Fri, 23 Mar 2018 13:19:58 +0100
-Subject: [PATCH 1/1] Don't fail on const/restrict/static/* inside []
-
-This patch makes tcc ignore them.
-
-Normally (as per the C standard), They should
-be only applicable inside parameter arrays
-and affect (const/restrict) the pointer the
-array gets converted to.
-
-[matz: fix formatting, add volatile handling, add testcase,
-add comment about above deficiency]
----
- tccgen.c                               | 19 +++++++++++++++++--
- tests/tests2/100_c99array-decls.c      | 34 ++++++++++++++++++++++++++++++++++
- tests/tests2/100_c99array-decls.expect |  0
- 3 files changed, 51 insertions(+), 2 deletions(-)
- create mode 100644 tests/tests2/100_c99array-decls.c
- create mode 100644 tests/tests2/100_c99array-decls.expect
-
-diff --git tccgen.c tccgen.c
-index 7ed89ac..6ef40e4 100644
---- tccgen.c
-+++ tccgen.c
-@@ -4335,8 +4335,23 @@ static int post_type(CType *type, AttributeDef *ad, int storage, int td)
- 	int saved_nocode_wanted = nocode_wanted;
-         /* array definition */
-         next();
--        if (tok == TOK_RESTRICT1)
--            next();
-+	while (1) {
-+	    /* XXX The optional type-quals and static should only be accepted
-+	       in parameter decls.  The '*' as well, and then even only
-+	       in prototypes (not function defs).  */
-+	    switch (tok) {
-+	    case TOK_RESTRICT1: case TOK_RESTRICT2: case TOK_RESTRICT3:
-+	    case TOK_CONST1:
-+	    case TOK_VOLATILE1:
-+	    case TOK_STATIC:
-+	    case '*':
-+		next();
-+		continue;
-+	    default:
-+		break;
-+	    }
-+	    break;
-+	}
-         n = -1;
-         t1 = 0;
-         if (tok != ']') {
--- 
-2.11.4.GIT
-