refactor(ports)!: streamlining and python support

[Yohe-Am]

Describe your change

• Simplify port interface, encapsulate globals
• Working directories for python/rust support
  • Working directories were found unnecessary
  • Python support
  • Rust support
• Port runtime dependencies

Motivation and context

These features appear necessary for good support of the python & rust toolchains. The concept of cache/share/working dirs seems like a good fit for package/environment managers.

Migration notes

• ghjk.ts scripts will need to use the install function from ghjk/mod.ts to add port installs. No more global aware function provided by ports
• Port impls are expected to rewrite large chunks.

Checklist

• The change come with new or modified tests
• Hard-to-understand functions have explanatory comments
• End-user documentation is updated to reflect the change

[Yohe-Am]

@zifeo Even the reduced scope of our python support required some...ridiculously hacky and fragile code but it's working now. The main reason for this difficulty due to how python sys vars are populated and the virtual environment creation and installation clashing with the isolation scheme in ghjk today. Some of the awkward python APIs aren't much help either. Will want to test these with more kinds of pip packages but it's worked with what I threw at it so far (poetry, pre-commit...).

Edit: might be be better you review this after I add comments on some of the sync code. (I'll do so ASAP)