Avoid conflict with existing projects and scripts when using `dangerously-allow-all-builds` globally

[tusharsnx]

Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

I can't easily use the global dangerously-allow-all-builds setting without conflicting with existing scripts (E.g. create-next-app) and projects that use --allow-build or onlyBuiltDependencies.

The workaround is to remove dangerously-allow-all-builds from the config first, and then run the script, but it's not a good experience. I believe this needs improvement.

Describe the solution you'd like

dangerouslyAllowAllBuilds should work as allow building all dependencies except when onlyBuiltDependencies is set. This should avoid the conflict, but still maintain the same setup on every machine.

Describe the drawbacks of your solution

No response

Describe alternatives you've considered

Relaxing the restriction completely. (This might introduce confusion regarding which dependencies were built based on the config.)

[tusharsnx]

The issue doesn't seem to have been fixed. The script still fails with the same error message.