[rush] Need a way to bypass the error raised by #4853

[GongT]

Summary

#4853

I have used this kind of dependencies for many years in my repo (it's gongt/baobao but not important). It break my workflow in recent update (rush version 5.131.0 -> 5.132.0)

Repro steps

Expected result: It should be a warning instead of an error. At least it must be configurable somewhere.

Actual result: Throw an error and no way to bypass.

Details

I have at least two scenarios require this. I will try to describe what I'm doing.

I have two package, Although they list each other in their dependencies, they don't really create any loop. The new check forcing me do an useless (sometimes impossible) decouple step.

example 1, private dependency loop

No way to bypass, this blocking me from upgrading rush version.

two package: builder and rig, list each other as dependency. But they both private. (extremely easy to decouple since rig is just a set of static files, without any build step)

builder require files in rig to build.
rig require builder to "run".

example 2, self-bootstrapping

two package: toolchain and library, both public.

1. toolchain runtime requires library. can be build with tsc
2. library build by ts-node toolchain/bin