feat: add phase-level latency metrics for container scans

[bdemeo12]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Adds support for receiving timing metrics from the container plugin and forwarding them to CLI analytics. This is the CLI-side companion to the plugin PR that instruments the container scan flow.

Snyk-docker-plugin PR: snyk/snyk-docker-plugin#804

Where should the reviewer start?

How should this be manually tested?

Link a local build of the plugin (with timing instrumentation), run snyk container test with --debug, and confirm timing metrics appear in the analytics payload.

What's the product update that needs to be communicated to CLI users?

internal analytics only, no user-facing change.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

	Warnings
⚠️	You've modified files in src/ directory, but haven't updated anything in test folder. Is there something that could be tested?

Generated by 🚫 dangerJS against a0fc9bf