feat: @warp-drive/core/{build-config,types}

[runspired]

This is the beginning of figuring out the mechanics of implementing the new core package.

One of the harder threads to pull is the build-config. The docs are generated from code that is not exported, many of the modules are intended to be virtual, and it has a combination of raw cjs, compiled to cjs, and esm modules.

I've been playing with three potential directions:

A) build-config going away in favor of just having @warp-drive/core

• upside all in one place
• downside | impossible as the individual packages would have a cycle

B) build-config re-exporting from @warp-drive/core

• upside, single source of truth
• downside | impossible as the individual packages would have a cycle

C) core re-exporting from @warp-drive/build-config

• upside, no cycles.
• downside, multiple sources of truth, docs must live in different files in core than where they live in @warp-drive/build-config

(C) Is the current implementation in this PR