fix(edgeone): discover Node functions before the project build

[Alumos]

Summary / 摘要

On a fresh EdgeOne deployment, the frontend build can succeed while /api/public/env_check returns the SPA HTML and only the four KV proxy Edge Functions are deployed. The Node backend entry was generated during pnpm run build, after the CLI had already decided which function builders to enable.

• Track a small cloud-functions/[[default]].js entry with an explicit onRequest export, so Node functions can be discovered before the project build.

• Generate the actual backend bundle at dist-server/edgeone-entry.js. The entry imports that bundle, keeping generated code out of Git and preventing it from being registered as an additional function route.

• Preserve the root catch-all to cover existing /api/*, download, WebDAV, S3 and SPA routes.

• Update ignore rules, middleware documentation and Build Verify. CI checks that the tracked entry exists before building and tests JSON diagnostics and SPA responses through both the entry and a second bundle.

• Remove an existing duplicate DbCipher type import that prevented pnpm run lint from passing.

• This PR has breaking changes.

• This PR changes public API, config, storage format, or migration behavior.

• This PR requires corresponding changes in related repositories.

Related Issues / 关联 Issue

Relates to #93.

Testing / 测试

Validated locally with Node 22.21.1 and pnpm 9.15.4:

• pnpm install --frozen-lockfile
• node scripts/fetch-frontend.mjs and pnpm run build:edge
• pnpm run lint
• node --import tsx --test src/backend/server/*.test.ts — 175 passed.
• node --test tests/edgeone-entry.test.mjs — 4 passed.
• Prettier check for the changed build, entry, middleware, workflow and regression test files; git diff --check.
• Official edgeone@1.6.41 CLI comparison using clean before/after snapshots: the original code completed its project build without producing a Node function; the fixed code produced .edgeone/cloud-functions/api-node/index.mjs with a single ^/(.*)$ route. Dependencies and official frontend assets were provided beforehand; the snapshot install command was a no-op and its build command was node scripts/build-edge.mjs.
• Started the CLI-generated Node function locally and requested /api/public/env_check and /api/public/init_status: both returned HTTP 200 and JSON diagnostic data. This check intentionally had no production storage binding; it verifies the handler and diagnostics, not production storage readiness.

An EdgeOne production redeployment has not been performed. After redeploying, verify that the Node function appears and /api/public/env_check returns JSON before investigating storage availability.

Checklist / 检查清单

• Read the linked CONTRIBUTING guidance.
• Changes follow the existing repository license and contribution policies.
• Formatted the changed JavaScript and workflow files with Prettier where applicable.
• Requested a specific maintainer review.

AI Disclosure / AI 使用声明

• This PR includes AI-assisted content.
• Tool used: Codex.
• Usage scope: implementation, regression tests, documentation, local verification and review assistance.
• AI-assisted commits include Co-authored-by attribution.

The user supplied the deployment symptoms, logs and proposed discovery fix, and requested this contribution. Codex implemented and reviewed the changes and ran the validation above. Human code review remains pending.