The Issue

• npx is not an existing ddev command.
• npx is an alias of npm exec -- that comes with the npm package, so no new code is needed.
• npx is used to run JS code without installing it, which is often for setup, init, demos, config, and other one time executions.

How This PR Solves The Issue

This allows users to ddev npx in the same way they can do ddev npm without having to do ddev exec npx.

Manual Testing Instructions

1. ddev config
2. ddev start
3. ddev npx -c 'echo hello' will say hello. Or any npx command like ddev npx @biomejs/biome init which will setup biomejs config in your project.

Automated Testing Overview

• The change is minor in the way that this is an alias of another command, npm, that already has a test, so if the npm test passes this should as well.
• There is also the consideration of how to make it not be flaky since it largely involves external network resources.

Because of those points, I decided to just check the simple local command execution part of npx via the -c flag. The test does a simple echo hello and checks if hello is returned. In combination with the above npm test, I think that should be sufficient without adding any network request to the system.

Release/Deployment Notes

Does this affect anything else or have ramifications for other code? Does anything have to be done on deployment?

Nope