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

Nobody has claimed this yet.

### What's going on?

running **any** `playwright-cli` command displays the following banner:

```
$ playwright-cli

╔════════════════════════════════════════════════════════════════════╗
║ 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

Reproduce the issue by running any playwright-cli command with an available update, then locate the CLI updater that prints the banner. Check how it chooses installation commands and handles package-manager minimum-age policies and monorepos. Done means repeated commands no longer produce misleading or excessive update instructions, with the chosen behavior covered by relevant CLI tests.

Written by the indexing model from the issue text.