Nusex

**New stuff:**

- The `migrate` command, allowing you migrate from v0.x config and templates to v1.x config and templates
- The `download` command, allowing you to download nusex assets whenever

**Breaking changes:**

- Priorities have changed a little with the NSX spec, and so the spec is now a little different. dev6 and onwards won't be able to load templates created in dev5 and below, so you will need to deploy in dev5, then rebuild in dev6. The maximum individual file size is now 4 GB, which should be plenty enough for everyone. You can use `nusex download` to download the new spec premade templates.

- Add dependency installation systems (non-functional on PyPy)
- Improve docs

**New additions:**

- The `deploy` command is good to go!
- A force option has also been included to allow users to force a deployment
- If you're using this from the scripting API, you can also set a path to deploy the template to

**Breaking changes:**

- `Builders` are now called `Blueprints`
- The "DATE" option in the version config is now "CALVER"

This doesn't really add anything for the user, but changes a lot in the backend:

- The `Template` and `Profile` classes no longer inherit from `Entity`
- `EntityError` has been split into `TemplateError` and `ProfileError`
- `...Encoder` and `...Decoder` classes have been merged into `...SpecIO` classes (one for each file standard)
- File modifications during template building are now handled through new "builders" (although there's only `PythonBuilder` at the moment, and it's hardcoded in)

These changes have been done to try and simplify the code a little and make it more understandable, and to make the docs nicer. The builders change allows for easy multi-language support later down the line -- just create a builder for a different language! There'll be CLI options and that later on to change the language once more are available, which probably won't be until at least v1.0 comes out, but the system is there, and it's cleaner anyways.

This release is mainly just cleaning up some code, and redoing the errors to make them more consistent, and more clear.

The currently implementation of extensions (albeit incomplete as it is) has been removed, to be replaced with a different system after deploying is written.