Update npm and composer commands to use site containers

[jasonmccallister]

Description

Right now, both of the npm and composer commands create a temporary container based on the path of the command. This is useful for running these commands on directories that will never be related to a "site" in Nitro context. However, the 80 percent use case is to run npm or composer within the context of a site. Therefore these commands should be more "site aware" but fall back to a standalone container if it cannot determine the part is part of a site.

We need to update the commands to use the sites container as those containers now include node, npm, and composer by default.

[jasonmccallister]

Hi, we are closing this issue as we have decided to retire Nitro, so no additional work will occur on this project. You can read the official blog post here https://craftcms.com/blog/retiring-craft-nitro. We appreciate everyones feedback and involvement and we look forward to refocusing our efforts on Cloud!

If you're looking for a new local development environment, we recommend DDEV and have a knowledge base article to help you with the transition: https://craftcms.com/knowledge-base/migrating-from-craft-nitro-to-ddev.