fix(wait): properly resolve kind when group conflicts between resources

[AustinAbro321]

Description

There is a bug in Zarf where running a wait command with a kind where there exists another kind of that name does not get properly resolved. For instance, zarf tools wait-for gateways.networking.istio.io admin-gateway would not work as it would try to resolve the default from Kubernetes gateway resource.

Versions don't matter in this context as they're considered the same object by Kubernetes, I tested this out with kubectl wait

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	e273286
🔍 Latest deploy log	https://app.netlify.com/projects/zarf-docs/deploys/6998c6857e4a3b0008c2bc79

[brandtkeller]

lgtm

[codecov]

Codecov Report

❌ Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/pkg/wait/wait.go	0.00%	7 Missing ⚠️

Files with missing lines	Coverage Δ
src/pkg/wait/wait.go	11.87% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.