Clarify dependency management options for buildable Node libraries

[DarylLyonsLF]

Documentation issue

• Reporting a typo
• Reporting a documentation bug
• Documentation improvement
• Documentation feedback

Is there a specific documentation page you are reporting?

https://nx.dev/concepts/decisions/dependency-management
https://nx.dev/ci/recipes/other/ci-deployment

Additional context or description

#19543 dropped support for generating package.json files during execution of @nx/js:tsc. The recommendation is to use @nx/dependency-checks instead.

This change results in package.json files existing on buildable Node libs where they weren't required before.

Nx docs relating to dep management seem to overlook this change. E.g.

1. https://nx.dev/concepts/decisions/dependency-management#single-version-policy
   Doesn't account for buildable lib's and is misleading in this context:

   Individual projects may still have package.json files, but they are used only for the metadata defined there, not as a way of defining the dependencies of that project.

2. https://nx.dev/ci/recipes/other/ci-deployment
   This page is linked from the single version policy page (above). It only accounts for application deployment - where can I find information on publishing lib's through CI, or options for managing their dependencies?