chore: Use context.Context from InvocationContext

[PeterSchafer]

Description

This PR includes a couple of refactorings to make use of the context.Context instance provided by the InvocationContext. This requires extending a couple of interfaces.

To keep the changes incremental, it doesn't yet fully use the context and needs to fallback to context.Background() where the context is not directly available yet.

Checklist

• Tests added and all succeed (make test)
• Regenerated mocks, etc. (make generate)
• Linted (make lint)
• Test your changes work for the CLI
  1. Clone / pull the latest CLI main.
  2. Run go get github.com/snyk/go-application-framework@YOUR_LATEST_GAF_COMMIT in the cliv2 directory.
     • Tip: for local testing, you can uncomment the line near the bottom of the CLI's go.mod to point to your local GAF code.
  3. Run go mod tidy in the cliv2 directory.
  4. Run the CLI tests and do any required manual testing.
  5. Open a PR in the CLI repo now with the go.mod and go.sum changes.
  • Once this PR is merged, repeat these steps, but pointing to the latest GAF commit on main and update your CLI PR.

[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.

[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.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 47 relevant code sections from 13 files (average relevance: 0.98) pkg/mocks/workflow.go (3 segments, lines 1-238) pkg/local_workflows/connectivity_check_extension/connectivity_check_workflow.go (lines 1-97) pkg/apiclients/ldx_sync_config/mocks/ldx_sync.go (lines 1-180) pkg/apiclients/feature_flag_gateway/client.go (lines 1-62) pkg/local_workflows/output_workflow/other_tools.go (lines 1-144) pkg/local_workflows/data_transformation_workflow.go (lines 1-125) pkg/apiclients/ldx_sync_config/ldx_sync/2024-10-15/ldx_sync.go (lines 1-223) ... and 6 more file(s)

[danskmt]

Some places are using invocationCtx.Context() and others context.Background(). I also see the latter was replaced by the former in some cases.
What is the difference between them? Should we have a unified way of having the context?