refactor: project utils

[brunozoric]

Changes

Remove project-utils usage from packages.

[github-actions]

🚓 Slop Cop

⚠️ 3 thing(s) worth a look before merging.

The PR is a large, coherent multi-commit refactor that systematically moves testing utilities out of project-utils into more appropriate packages (api-core, db-dynamodb, background-tasks, api, api-opensearch-aws), matching its stated intent; the size (208 files) is explained by the mechanical nature of import-path updates and tsconfig/package.json path fixes across many packages, not by unrelated deletions.

🚨 Should this be in the PR?

🟡 Low — Unrelated dependency/version bumps included in refactor PR

Many package.json files across the repo have unrelated version bumps (e.g. cypress, nanoid, storybook, aws-sdk, next, oxlint, better-sqlite3, pg, tsx, etc.) alongside the project-utils migration. This is likely from a lockfile/deps update commit ('chore: update project-utils deps and lockfile') but inflates the diff far beyond the stated 'remove project-utils usage' intent. Not a red flag of accidental deletion, but reviewers should confirm these version bumps are intentional and not from a stale branch merge.

📏 Code-style rule checks

🟠 Medium — console.log used in simulateStream.ts error path

packages/api-opensearch-aws/src/testing/simulateStream.ts (new file) uses console.log(JSON.stringify(command)); in the catch block. While this is testing utility code (not strictly api-* backend runtime code), it's a stray debug statement carried over from the old project-utils code and should probably use a logger or be removed per no-console-in-backend.md intent (this package is api-opensearch-aws, an api-* package).

🟡 Low — Non-standard comment style in ExperimentsEditorPresenter.ts diff

packages/app-website-builder/.../ExperimentsEditorPresenter.ts shows a reformatting of .map() call (removing parens/indentation) unrelated to project-utils removal; not a rule violation per se, but appears to be unrelated formatting churn possibly from a lint/format pass, worth double-checking scope.

_{Automated, non-blocking heads-up from an LLM. It can be wrong — use your judgment. Regenerates on every push.}