Updated detection of Node and Japa test runners

[fabnguess]

This PR aims to improve the detection of test runners used in projects, particularly for Node.js and Japa.

Currently the code only checks the test script in the package.json file. However, in many projects it is the test-only script that is responsible for running the tests. This prevents correct detection of Node's test runner.

Proposed changes:
Test-only script support: The code has been changed to also check the test-only script in the package.json file, in addition to the test script.

Japa verification: As per Japa documentation, the presence of @japa/runner in devDependencies is now checked to identify projects using Japa as a test runner.

[PierreDemailly]

I think we can go further by checking if the test script contains another script instead of looking for test-only specifically.
For instance, we can imagine something like this:
"test": "npm run test:ut && npm run test:ft"
And many other patterns.

In this example, we can detect that test:ut and test:ft are used in the test script, so we'll check both of them, recursively (if test:ut contains another script then we'll check it, etc).

Another way would be checking all scripts that contains (or starts with) test, so if we keep the first example, we'll detect that both test:ut and test:ft contains or starts with test then we'll check these scripts.
This way is probably simpler, WDYT?

[fabnguess]

I @PierreDemailly, The second approach seems easier to implement, while the first one offers greater flexibility. So, which solution would you prefer us to focus on?

[fabnguess]

Well rated

[PierreDemailly]

@fabnguess Nevermind i'm dumb 🤣
We detect these runners by checking if they are present in (dev) deps, script does not matter.