Adapt `clever-tools` update command based on the package manager

[maximepvrt]

Currently, when a new version of clever-tools is available, the message shown is:

Update available 3.13.1 → 4.4.0
Run npm i -g clever-tools to update

This assumes the user is using npm, while some users may be using pnpm, yarn, brew, etc.

Proposal:

• Detect the package manager in use or display multiple commands for different environments:

  • npm: npm i -g clever-tools
  • pnpm: pnpm add -g clever-tools
  • yarn: yarn global add clever-tools
  • brew: brew upgrade clever-tools

• Dynamically show the appropriate update command based on the user’s environment.

Expected benefits:

• Reduce update errors.
• Provide a smoother experience for all users.
• Ensure consistent support for different package managers.

[hsablonniere]

Hello @maximepvrt,

• This message is handled by a dependency called update-notifier and they don't want to support such a feature
  • [FR] Support pnpm sindresorhus/update-notifier#231
• Installs via other means than npm or its alternatives don't use update-notifier so homebrew is not part of this

I have a fairly similar opinion to Sindre Sorhus about having to maintain a list of npm alternatives. Especially since once you have several on your machine, it becomes difficult to know which one was used (npm, pnpm, yarn, bun install...). However, we had already discussed having this message/mechanism for other install methods as well (brew, AUR, WinGet, deb, rpm...). I'm keeping the issue open so we can reconsider it, but it won't be a priority for now.