Should we break out VirtualEnv into its own project?

[nickjalbert]

I think there's a chance some people would find programmatic virtual env management useful, even if they didn't need or want the other features of PCS/AOS for their project. VirtualEnv is pretty self contained, I think it'd be cool to break it out into its own repo and package so projects (including PCS and AOS) could just pull in that as a relatively-small-in-scope dependency.

Downside is that it'd take more overhead to manage (and release etc).

Upside is that it might introduce people to AOS ecosystem (esp. if it still lives under the banner of agentos-project) and it might be easier to get community contributions to the venv package since the scope is pretty constrained.