Initial Implementation: Configuration hosting

## Summary

To begin with, we focus on the most important feature of structe, which is to remove configuration and building stages of a frontend project.

You can look at the tool like abstracting your dev dependencies and build commands to its own repository, where we expose a simple API to generate a build, run a tool, or and to have a cleaner project root.

To eject structe, you can do that through our api, and get the abstracted tools into your projects again. Good for things like CI's and production branches.

## Needed Functionality in crates

- Config/builder crate
- (Not initally needed): Tools folder
- Context manager that is used together with builder crate
- Resolver crate (To resolve schemas from the CLI)
- Bootstrapping (Creating a structe project)
- CLI with init
- CLI with commands
- PkgJSON path to structe project path

We will initially have the functionality like a configuration picker, where the user can swap between configurations and output to pwd or config pwd given through a flag/config option.