[Bug?]: Yarn v4.3.1 does not exit when "No upgrades found" with `yarn upgrade-interactive`

Self-service

[ ] I'd be willing to implement a fix

Describe the bug

I expect Yarn to exit when "No upgrades found" with yarn upgrade-interactive. Instead it stays open until I close it with CTRL+C.

This is using PowerShell v7.4.3 x64 in VSCode v1.90.2 x64 on Windows 11 23H2. NodeJS installed with fnm fnm env --corepack-enabled; fnm install --lts, corepack enabled, in a project with package.json has "packageManager": "yarn@4.3.1+sha512.af78262d7d125afbfeed740602ace8c5e4405cd7f4735c08feb327286b2fdb2390fbca01589bfd1f50b1240548b74806767f5a063c94b67e431aabd0d86f7774".

PS > yarn upgrade-interactive
 Press <up>/<down> to select packages.            Press <enter> to install.
 Press <left>/<right> to select versions.         Press <ctrl+c> to abort.

? Pick the packages you want to upgrade.          Current          Range            Latest

No upgrades found

To reproduce

yarn upgrade-interactive with no packages to upgrade.

Environment

System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
  Binaries:
    Node: 20.15.0 - C:\Users\OLAV~1.BIR\AppData\Local\Temp\xfs-c8e5f2e0\node.CMD
    Yarn: 4.3.1 - C:\Users\OLAV~1.BIR\AppData\Local\Temp\xfs-c8e5f2e0\yarn.CMD
    npm: 10.7.0 - ~\AppData\Local\fnm_multishells\15304_1719993716062\npm.CMD
    bun: 1.1.17 - ~\scoop\shims\bun.EXE

Additional context

No response

yarnpkg / berry