fix: don't save lockfile if --frozen-lockfile or --no-save

[pikdum]

What does this PR do?

When running bun install --frozen-lockfile against a project with a package.json and package-lock.json, this brings back behavior of not creating a bun.lock file. (Regression?)

This also gives bun install --no-save the same behavior. (Not sure if it ever worked when migrating.)

Closes #16646
Closes #16965

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

$ bun install --frozen-lockfile &> /dev/null && ls bun.lock && rm -f bun.lock
bun.lock
$ bun-debug install --frozen-lockfile &> /dev/null && ls bun.lock
ls: cannot access 'bun.lock': No such file or directory

Added some automated tests, too:

$ bun run test 16646

And verified that the tests fail against current main.

[dylan-conway]

We should check for this flag before calling this function. The bug exists in the long chain of or's and and's used to create should_save_lockfile. this.options.do.save_lockfile is already checked, so likely it's not checked early enough.

[pikdum]

Moved there: eb649a4

[dylan-conway]

See above