fix: status check connecting to the wrong k8s context

[ericzzzzzzz]

Fixes: #8970

Description

• The original way to create k8s client for status check seems a typo, not intended.
• We should use the kubeContext to initiate kubeClient instead of kubeConfig
• Using kubeConfig causes status check against active context that user host is connected, we should instead do the check against kube context users set up for skaffold.

[codecov]

Codecov Report

Merging #8981 (4fee549) into main (290280e) will decrease coverage by 6.84%.
Report is 987 commits behind head on main.
The diff coverage is 49.80%.

@@            Coverage Diff             @@
##             main    #8981      +/-   ##
==========================================
- Coverage   70.48%   63.64%   -6.84%     
==========================================
  Files         515      624     +109     
  Lines       23150    31941    +8791     
==========================================
+ Hits        16317    20330    +4013     
- Misses       5776    10081    +4305     
- Partials     1057     1530     +473     

Files Changed	Coverage Δ
cmd/skaffold/app/cmd/completion.go	13.04% <0.00%> (-1.25%)	⬇️
cmd/skaffold/app/cmd/config/list.go	65.21% <ø> (ø)
cmd/skaffold/app/cmd/config/set.go	88.72% <ø> (ø)
cmd/skaffold/app/cmd/config/util.go	54.28% <ø> (ø)
cmd/skaffold/app/cmd/credits.go	100.00% <ø> (ø)
cmd/skaffold/app/cmd/credits/export.go	0.00% <0.00%> (ø)
cmd/skaffold/app/cmd/deploy.go	40.90% <0.00%> (-12.94%)	⬇️
cmd/skaffold/app/cmd/generate_pipeline.go	60.00% <ø> (ø)
cmd/skaffold/app/cmd/inspect_modules.go	65.00% <ø> (ø)
cmd/skaffold/app/cmd/inspect_profiles.go	66.66% <ø> (ø)
... and 40 more

... and 415 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more