Use qa/expect/js-npm for js-npm@offline-FREEZE

What does this MR do?

Use the normal expected report for js-npm when running a downstream pipeline using the offline-FREEZE branch.

This fixes the downstream pipeline. It's been broken since we've merged gitlab-org/security-products/tests/js-npm!13568 (merged).

What are the relevant issue numbers?

None

Does this MR meet the acceptance criteria?

• [NA] Changelog entry added
• Documentation created/updated for GitLab EE, if necessary
• Documentation created/updated for this project, if necessary
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Job definition updated, if necessary
  • Auto-DevOps template
  • Job definition example
  • CI Templates
• Conforms to the code review guidelines
• Conforms to the Go guidelines
• Security reports checked/validated by reviewer