src: define O_SYNC, O_DSYNC and O_DIRECT on Windows - #64707

Signed-off-by: Kirill Saied <[email protected]>
PR-URL: #64707
Reviewed-By: Stefan Stojanovic <[email protected]>
Reviewed-By: James M Snell <[email protected]>

Signed-off-by: Kirill Saied <[email protected]>
PR-URL: #64707
Reviewed-By: Stefan Stojanovic <[email protected]>
Reviewed-By: James M Snell <[email protected]>

## Summary

Raises the `aws-cdk-lib` peer dependency floor from `^2.234.1` to
`^2.254.0` across all packages and refreshes the lockfile (now resolves
`aws-cdk-lib` to `2.267.0`).

## Why

On Windows with recent Node.js releases, CDK asset fingerprinting
crashes with `EINVAL` because `fs.openSync` is invoked with the `O_SYNC
| O_DSYNC` flag combination, which Node rejects on that platform. This
makes the Windows unit/coverage job fully red while Linux and macOS stay
green.

The crash was fixed upstream in aws-cdk and first released in
`aws-cdk-lib` 2.254.0. Bumping the floor to `^2.254.0` pulls in the fix.

- Upstream issue: aws/aws-cdk#38692
- Upstream fix (PR): aws/aws-cdk#37802 (released
in `aws-cdk-lib` 2.254.0)
- Related Node.js change: nodejs/node#64707

## What changed

- Bumped `aws-cdk-lib` from `^2.234.1` to `^2.254.0` in all 16
`packages/*/package.json` files (peer/dep/devDep as applicable). No
other dependencies changed.
- Refreshed `package-lock.json` — `aws-cdk-lib` now resolves to
`2.267.0` (latest within the range), deduped across the workspace.
- Updated `packages/create-amplify/src/default_packages.json` so the
default `aws-cdk-lib` pin for new projects matches the lockfile
(generated via `npm run update:create-amplify-deps`).
- Added a changeset (patch bump for affected published packages).

## How tested

- `npm install` + `npm run build` — clean.
- Ran the unit/integration suites. All CDK-heavy suites pass (in-memory
CDK synthesis integration tests, `auth-construct`, `backend-storage`,
`backend-data`): 280/280.
- No CDK-generated construct snapshots/logical IDs changed as a result
of the bump, so no snapshot regeneration was needed.
- `check:package-lock`, `check:package-json`, `check:api`, and prettier
all pass.

The only local failures were in `platform-core` config/telemetry tests
that write to a real user-profile path; these fail identically with and
without this change in the local sandboxed environment
(permission-restricted `~` path) and are unrelated to the CDK bump.

---------

Co-authored-by: sarayev <[email protected]>