[BUG] Playwright CLI updater does not respect supply chain policies and spams the console

What's going on?

running any playwright-cli command displays the following banner:

$ playwright-cli <command>

╔════════════════════════════════════════════════════════════════════╗
║ Update available for @playwright/cli: 0.1.18 → 0.1.19              ║
║ Run `npm install -g @playwright/cli@latest` (global) or            ║
║ `npm install --save-dev @playwright/cli@latest` (local) to update. ║
╚════════════════════════════════════════════════════════════════════╝

This does not respect minimum-age supply chain policies of the package manager (the package can not be updated since it's not old enough). Running these commands will not update the package.

Since usually you run several commands in succession, this quickly fills the console logs with large useless banners.

Also, it does:

• not respect the current package manager (eg. pnpm etc.), creating potential confusion.
• commands are wrong for monorepos in which the dependency is not necessarily in the current package.json.
• the package has been installed anyway by the user, so displaying how to install packages seems somewhat redundant...

Overall, this seems that it can cause more potential confusion with inaccurate instructions than it adds positive value.

Version

cli 0.1.18