fix(build): resolve @stacksjs/actions subpath when compiling the CLI (#2247)

`"@stacksjs/*": ["./*/src"]` binds the wildcard to the whole remainder, so
`@stacksjs/actions/blog` looked for `./actions/blog/src`, missed, and fell back
to `actions/dist/blog.js` — which nothing builds before the compile job:

  error: Could not resolve: "@stacksjs/actions/blog"
    at core/buddy/src/production-server.ts:370:53
  error: script "compile:linux-x64" exited with code 1

This is the same entry I added in #2223 and then removed, because it appeared
to turn `core/config` and `core/env` tests red. It did not. That was the
load-order race in the config overrides fallback, fixed in #2246 — the entry
perturbed module resolution enough to expose it, which is also how a package.json
dependency in #2244 managed to "break" the same two packages.

With #2246 landed, `core/config` + `core/env` pass locally with this applied
(322 tests), and the CLI bundles 1933 modules and links.

Closes #2242

Author: glennmichael123

storage/framework/core/tsconfig.build.json

@@ -17,6 +17,13 @@
     "moduleResolution": "bundler",
     "paths": {
       "~/*": ["../../../*"],
+      // `@stacksjs/*` below binds the wildcard to the whole remainder, so
+      // `@stacksjs/actions/blog` looks for `./actions/blog/src`, misses, and
+      // falls back to the package's unbuilt `dist/`. Bun honours these mappings
+      // during `bun build`, so without this entry `buddy compile:*` cannot
+      // resolve the blog feed renderer on a checkout that has not built every
+      // package, which is every CI run.
+      "@stacksjs/actions/*": ["./actions/src/*"],
       "@stacksjs/*": ["./*/src"],
       "ts-pantry": ["../../../node_modules/ts-pantry"],
       "*": ["../../../pantry/*"]