Add max scan duration to analyzer's downstream jobs

What does this MR do?

This MR adds the MAX_SCAN_DURATION_SECONDS variable to each downstream test job in order to have the pipeline fail when the current analyzer build's scan duration has increased.

The max duration was tested by setting the variable to 0 and having it fail with the true scan duration:

• pipeline used to measure baseline: https://gitlab.com/gitlab-org/security-products/analyzers/retire.js/-/pipelines/215946544
• passing pipeline with new MAX_SCAN_DURATION_SECONDS: https://gitlab.com/gitlab-org/security-products/analyzers/retire.js/-/pipelines/215950794

Note: a CHANGELOG entry was not set for this MR.

What are the relevant issue numbers?

gitlab-org/gitlab#196697 (closed)

Does this MR meet the acceptance criteria?

• 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