Add depth and isDevDependency CSV columns / module info; recurse direct dependencies

[laurence-myers]

This adds the option to include the columns depth and isDevDependency when outputting CSV files. This allows you to easily filter the data later - e.g. you can produce a single file containing all dev dependencies, and dependencies from any depth, and then filter the data later to only show the direct dependencies (depth = 1) or Prod dependencies isDevDependency = false.

I found that the tool was iterating dependencies, which seems to be a flat array of all dependencies. I changed it to iterate _dependencies, which only includes the direct dependencies. This gives proper values of depth and isDevDependency based on whether the parent was a dev dependency. I haven't fully tested the consequences of this (the unit tests do not run in NodeJS v24, because it tries to load CommonJS modules as ECMAScript modules).

There might be a better name for these new columns.

I based this off tag v4.4.2, because master had an issue (the bin does not work because it tries to call the function parse(), but it was renamed to parseArgs()), so I didn't know what the current state of development was.

[laurence-myers]

Needs some work; recursion doesn't work how I expected, so the depth and dev values are incorrect. I also need to add tests.

[laurence-myers]

I was unable to run the unit tests, they do not run in NodeJS v24, because the unit tests are written as CommonJS modules, but NodeJS tries to load them as ECMAScript modules, due to the presence of "type": "module" in package.json.

As such, I have not added a unit test.

Fixing the existing unit test execution was out of scope for this PR.