refactor: context usage in k8s code

[lucasrod16]

Description

refactor context usage in k8s code

Related Issue

Relates to #2365

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	fc58ef2
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/6644b350baf89a000861893b

[phillebaba]

@lucasrod16 I had a deeper look at the k8s package and am now wondering why we even have it. Ignoring some helper functions, it for the most part just wraps a single call to the client set. In a sense it just increases complexity. My suggestion is to remove it and just use the client set directly.

[lucasrod16]

@lucasrod16 I had a deeper look at the k8s package and am now wondering why we even have it. Ignoring some helper functions, it for the most part just wraps a single call to the client set. In a sense it just increases complexity. My suggestion is to remove it and just use the client set directly.

Removing the k8s package could be something we discuss as a team, but it is out of scope for this PR. This PR is more strictly focused on how context flows through the program to the client set.

[phillebaba]

I think this looks fine. I still have some thoughts about using timer.Reset but we can revisit that at a later PR. It is a lot more valuable to get this merge to unlock a lot of other fixes.