Don't display internal libs in the output of the `deps` command

[infomiho]

Based on this comment #2989 (comment)

We include the internal libs (WaspLibs) in the output of the deps command.

This is problematic because we tell users in the deps command output:

You can import and use these directly in the code as if you specified them yourself

which implies that Wasp libs are fair game.

This happens because deps reuses the same function (npmDepsForWasp) that's used internally in the Generator to generate the package.json for server and web-app.

We should find a way to decouple the deps command and the Generator. We probably need a new concept of "user usable framework deps" and "internal framework deps".

[Martinsos]

Hm I think we actually do have maybe that split. But I know we were showing them on purpose before, because they coudln't install their own if there was a version of our. That might have changed so that is also to be taken into account. I am just trying to offer some historical data here.

[Martinsos]

Duplicate/part of #2906 . Also re-evaluate since we merged npm workspaces, that might help.