feat(settings): move NeoPi launch and connection configuration into NeoCore #136

No, I wouldn't even put like display name or runtime, profile, launch arguments, environment variables. This doesn't belong here, because this is like config, like startup config. I would put this under a section called something like system, or runtime, actually. Yeah, considering the runtime is gonna be a very important thing that comes up often, I would make a whole section on the left called runtime and move binary path, profile, launch arguments, and environment variables to a section on the left called runtime, which, believe me, it will increase in size. Because when we start connecting NeoDeck to it, and we start connecting Neo, like, NeoProxy to it, runtime is gonna, you know... Or maybe we should call it NeoCore. Make a section called NeoCore and make all that has to do with, like, launching everything just be in there. Or, like, launching and connecting to all the other Neo services, let's say. Neo processes. The NeoCore daemon. Which is ultimately what I'm gonna have to create to bridge all these different things together is a daemon service that I can launch MPI under. So I can run like MPI like core D, right, as a subcommand. And when I'm able to do that, and I can daemonize MPI and have it not be a terminal user interface, but just be a core daemon that basically exposes the harness's guts and internals and allows you to, you basically could just communicate with that, you know, daemon and be like, hey, daemon, I need an agent, right? Can you create an agent? and you just communicate over, you know, maybe WebSocket for compatibility. You just tell it, I need a, I need a, yeah, I just need an agent. And at that point, what protocol do we use? Do we just send everything over JSON? These are questions I should be asking a whiteboard agent, but maybe it'll have some insights. but yeah, make a section on the left called NeoCore. Move the runtime area from the providers section inside of Neo, like the NeoPy section inside of the providers section, where it says setup, runtime, binary path, profile, launch arguments, and then environment, and then, there we go to the juicy part, models, right? That section where it says models, where it's just relegated to this little piece at the bottom of the provider, like, that should be the entire provider screen. That should be the whole page. Everything else should be gone.