fix(client): let a caller context reach the report upload

[ArneshBanerjee]

Fixes #58

SubmitReport takes no context, so the report POST always ran with context.Background(). Kubescape checks ctx.Err() between report chunks, but once an upload was on the wire nothing could stop it, and a cancelled scan or a shutdown had to wait out the client timeout.

This adds SubmitReportWithContext(ctx, report, opts...) and keeps SubmitReport as a wrapper over it with context.Background(), so existing callers are unchanged. The context goes through the WithContext request option that is already used by get/post, so no new plumbing was needed. This is the same shape as GetExceptionsWithContext and GetControlsInputsWithContext from #57.

Tests use a recording RoundTripper that can block until the request context is done, and cover:

• the caller context reaching the transport
• cancelling after the request has started, returning promptly with context.Canceled
• a deadline surfacing as context.DeadlineExceeded
• request options still applying alongside the context
• SubmitReport behaving as before

Verified locally with go build ./..., go test ./... and go test -race ./..., all passing. go vet ./... reports four copylocks findings in pkg/server/v1/systemreports/datastructures_test.go, which are present on main before this change and are untouched here.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6e70556a-7a57-4c0f-9dd0-7834d8c854c4

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[matthyx]

Reviewed against #58's acceptance criteria — all met:

• SubmitReportWithContext(ctx, report, opts...) is additive; SubmitReport stays a thin wrapper over context.Background(), so existing callers are unaffected.
• The context reaches the transport via the existing WithContext request option → http.NewRequestWithContext, same shape as GetExceptionsWithContext/GetControlsInputsWithContext from #57.
• opts = append([]RequestOption{WithContext(ctx), WithContentJSON(true)}, opts...) preserves the original WithContentJSON(true) behavior for callers while still letting explicit opts win, consistent with the functional-options pattern in kscloudoption.go.
• The recording RoundTripper tests are solid: they verify the context value reaches the request, that cancelling an in-flight (blocked) request surfaces context.Canceled, that a timeout surfaces context.DeadlineExceeded (both checked with errors.Is, so they survive the *url.Error wrapping from http.Client), that extra request options still apply, and that plain SubmitReport still works.
• Checks are green (GitGuardian, DCO); the go vet copylocks findings mentioned in the description are pre-existing on main and untouched here.

No blockers. Approving.