(aws-lambda-nodejs): bun depenedencies fail with `error: lockfile had changes, but lockfile is frozen`

### Describe the bug

When a `bun` lockfile contains additional entries compared to what's installed in the docker container at bundling time, the bundling fails with this error:

```shell
error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile
```

### Regression Issue

- [ ] Select this option if this issue appears to be a regression.

### Last Known Working CDK Version

N/A - this is new behavior I implemented against #31753

### Expected Behavior

I expect changes to the lockfile to be allowed and the synth to pass.

### Current Behavior

```shell
error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile
```

### Reproduction Steps

See https://github.com/blimmer/cdk-bug-reports/pull/3 for a working repro case.

### Possible Solution

We need to not enforce `--frozen-lockfile`, like we do for other package managers: https://github.com/aws/aws-cdk/blob/fb2b229912f7400f810959eeb51008e680216718/packages/aws-cdk-lib/aws-lambda-nodejs/lib/package-manager.ts#L34-L49

### Additional Information/Context

_No response_

### CDK CLI Version

2.175.1

### Framework Version

_No response_

### Node.js Version

22 LTS

### OS

MacOS

### Language

TypeScript

### Language Version

_No response_

### Other information

_No response_

	case LockFile.YARN:
	return new PackageManager({
	lockFile: LockFile.YARN,
	installCommand: logLevel && logLevel !== LogLevel.INFO ? ['yarn', 'install', '--no-immutable', '--silent'] : ['yarn', 'install', '--no-immutable'],
	runCommand: ['yarn', 'run'],
	});
	case LockFile.PNPM:
	return new PackageManager({
	lockFile: LockFile.PNPM,
	installCommand: logLevel && logLevel !== LogLevel.INFO ? ['pnpm', 'install', '--reporter', 'silent', '--config.node-linker=hoisted', '--config.package-import-method=clone-or-copy', '--no-prefer-frozen-lockfile'] : ['pnpm', 'install', '--config.node-linker=hoisted', '--config.package-import-method=clone-or-copy', '--no-prefer-frozen-lockfile'],
	// --config.node-linker=hoisted to create flat node_modules without symlinks
	// --config.package-import-method=clone-or-copy to avoid hardlinking packages from the store
	// --no-prefer-frozen-lockfile (works the same as yarn's --no-immutable) Disable --frozen-lockfile that is enabled by default in CI environments (https://github.com/pnpm/pnpm/issues/1994).
	runCommand: ['pnpm', 'exec'],
	argsSeparator: '--',
	});

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(aws-lambda-nodejs): bun depenedencies fail with `error: lockfile had changes, but lockfile is frozen` #32906

Describe the bug

Regression Issue

Last Known Working CDK Version

Expected Behavior

Current Behavior

Reproduction Steps

Possible Solution

Additional Information/Context

CDK CLI Version

Framework Version

Node.js Version

OS

Language

Language Version

Other information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

(aws-lambda-nodejs): bun depenedencies fail with error: lockfile had changes, but lockfile is frozen #32906

Description

Describe the bug

Regression Issue

Last Known Working CDK Version

Expected Behavior

Current Behavior

Reproduction Steps

Possible Solution

Additional Information/Context

CDK CLI Version

Framework Version

Node.js Version

OS

Language

Language Version

Other information

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

(aws-lambda-nodejs): bun depenedencies fail with `error: lockfile had changes, but lockfile is frozen` #32906