chore: Invoke engine with instrumentation collector

[PeterSchafer]

Pull Request Submission Checklist

• [x] Follows CONTRIBUTING guidelines
• [x] Commit messages are release-note ready, emphasizing what was changed, not how.
• [x] Includes detailed description of changes
• [x] 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?

This PR makes use of the new capability to invoke workflows with a specific instrumentation collector, rather than using the default the instrumentation collector by default. This PR doesn't change any functionality, it just uses the new explicit invocation.

The risk of this PR is low, as it is only affects instrumentation and keeps the same behaviour.

Where should the reviewer start?

https://github.com/snyk/go-application-framework/pull/370

How should this be manually tested?

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

[snyk-io[bot]]

:tada: Snyk checks have passed. No issues have been found so far.

:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)

:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)

:white_check_mark: code/snyk check is complete. No issues have been found. (View Details)