chore: Re-structure workspaces, enforce build order

These are some changes in the way the monorepo is structured,
that are aimed at making it easier to get started.

There are two important changes:

**Multiple workspaces**

We had a yarn workspaces setup at `packages/*`. But our monorepo has
grown to 92 packages which can be overwhelming for people not familiar
with the package names.

To remedy this, I've split it into 4 different workspaces:

- `designs/*`: Holds FreeSewing designs (think patterns)
- `plugins/*`: Holds FreeSewing plugins
- `packages/*`: Holds other packages published on NPM
- `sites/*`: Holds software that is not published as an NPM package,
  such as our various websites and backend API

This should make it easier to find things, and to answer questions like
*where do I find the code for the plugins*.

**Updated reconfigure script to handle build order**

One problem when bootstrapping the repo is inter-dependencies between
packages. For example, building a pattern will only work once
`plugin-bundle` is built. Which will only work once all plugins in the
bundle or built. And that will only work when `core` is built, and so
on.

This can be frustrating for new users as `yarn buildall` will fail.
And it gets overlooked by seasoned devs because they're likely to have
every package built in their repo so this issue doesn't concern them.

To remedy this, we now have a `config/build-order.mjs` file and the
updated `/scripts/reconfigure.mjs` script will enforce the build order
so that things *just work*.

sites/freesewing.shared/components/workbench/draft/error.js

@@ -0,0 +1,69 @@
+import { useState } from 'react'
+import Robot from 'shared/components/robot/index.js'
+import Popout from 'shared/components/popout.js'
+import { useTranslation } from 'next-i18next'
+
+const Error = ({ draft, patternProps, error, updateGist }) => {
+
+  const { t } = useTranslation(['errors'])
+  const [share, setShare] = useState(false)
+
+  return (
+    <div className="max-w-4xl m-auto">
+      <Popout warning>
+        <div className="flex flex-row justify-between">
+          <div>
+            <h3>{t('errors:something')}</h3>
+            <p>Don't be alarmed, but we ran into some trouble while drafting this pattern.</p>
+          </div>
+          <Robot pose='fail' />
+        </div>
+      </Popout>
+      <Popout tip>
+        <h3>Would you like to report this problem?</h3>
+        <p>
+          You can help us <strong>make FreeSewing better by reporting this problem</strong>.
+        </p>
+        <p>If you choose to report this:</p>
+        <ul className="list-disc list-inside ml-4 text-xl">
+          <li>
+            We will compile a <strong>crash report</strong> that contains everything needed <strong>to recreate this problem</strong>
+          </li>
+          <li>
+            We will include <strong>personal data</strong> such as your <strong>username</strong>, <strong>
+            email address</strong> and <strong>measurements</strong>
+          </li>
+          <li>
+            We will share this report and the data in it with <a className="text-primary font-bold"
+            href="https://github.com/orgs/freesewing/teams/bughunters">FreeSewing's bughunters team</a> who will investigate the problem on your behalf
+          </li>
+          <li>Your personal data will <strong>not be shared publicly</strong></li>
+        </ul>
+        <div className="form-control">
+          <label className="cursor-pointer flex flex-row gap-4 my-4">
+            <input type="checkbox" checked={share} className="checkbox checkbox-primary" onChange={() => setShare(!share)}/>
+            <span className="label-text text-xl">I agree to the use of my personal data for the purposes outlined above</span>
+          </label>
+        </div>
+        <p>
+          <button disabled={!share} className="btn btn-primary">Report this</button>
+        </p>
+        <p>
+          If you prefer not to share any info, or want to investigate the problem yourself, you can do so:
+        </p>
+        <ul className="list-disc list-inside ml-4 text-xl">
+            <li>
+              Check the <button className="btn-link" onClick={() => updateGist(['_state', 'view'], 'events')}>
+              <strong>{patternProps.events.error.length} errors</strong> and <strong>
+              {patternProps.events.warning.length} warnings</strong></button>
+            </li>
+            <li>Check the partially rendered pattern below to see which areas are problematic</li>
+        </ul>
+      </Popout>
+    </div>
+  )
+}
+
+
+export default Error
+