[Nodejs] Update iast stack trace tests

[IlyasShabi]

Motivation

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[cbeauchesne]

Hi @IlyasShabi , @uurien, @iunanua

For later PR/reviews => this change modifies a test. I'm quite confident that it'll be ok because the integration scenario is very close to the default scenario. But rule of thumb, it's better to not use a prefix ([nodejs]) in the title in that use case, to be 100% sure we don't break anything. Otherwise, we'll face complaint in apm-shared-testing 😉

[IlyasShabi]

Hi @cbeauchesne the nosql_mongodb_injection stack trace test was not working due to this missing scenario, which is why we introduced this line.
As you can see in the PR history, I ran tests for all languages to ensure nothing was broken, and then I switched to [Nodejs] for minor changes, like updating dd-trace-js versions

[cbeauchesne]

Nice :) I didn't noticed this succesion of event 👍

AGTM, as long as no issue is introduced 😉