feat: better instructions on package manager installation failure

[micalevisk]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: close #1499

What is the new behavior?

display this message instead (taking PNPM as example):

🙀  Packages installation failed!
In case you don't see any errors above, consider manually running the failed command pnpm install to see more details on why it errored out

Also, I've replaced the --silent of PNPM by --reporter=silent (v6)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Instead of hard coding the full instalation command that might not be wrong by itself, I think is better to rely on the failed command.

As we couldn't access the binary name directly (nor its args) due to how it was defined on AbstractRunner abstract class and build the command by yourself, I've added another method on AbstractRunner class to expose a 'raw' version of some command

[kamilmysliwiec]

LGTM