In an extension, Loopback CLI depends on @loopback/core in list of dependencies

Describe the bug

Running CLI commands such as lb4 model in a loopback extension cause the commands to be aborted.

Generation is aborted: Error: No `@loopback/core` package found in the "dependencies" section of C:\Users\Ben\Documents\dev\customer-service\extensions\intercom\package.json. The command must be run in a LoopBack project.

This is because @loopback/core is not listed in dependencies. Yes it is both a devDependency and a peerDependency in a loopback extension. This was last discussed in #2163 and implemented in #2166.

Wouldn't it be a better developer experience if the command accepted @loopback/core as a peerDependency?

Logs

$ lb4 model

No change to package.json was detected. No package manager install will be executed.
Generation is aborted: Error: No `@loopback/core` package found in the "dependencies" section of C:\Users\Ben\Documents\dev\customer-service\extensions\intercom\package.json. The command must be run in a LoopBack project.

Additional information

No response

Reproduction

n/a

Commencez par le point d’entrée CLI lb4 model et suivez la vérification des dépendances qui signale l’absence du package @loopback/core. Reproduisez la commande dans une extension LoopBack où @loopback/core est une peerDependency ; le travail est terminé lorsque la commande est acceptée sans que ce package soit requis dans dependencies.