Set output event context in cache check, tag generation, status check, port forward

[MarlonGamez]

related: #5368

Description
This PR makes more calls to output.WithEventContext() in order to have SkaffoldLogEvents properly tagged for those parts of execution. This helps IDEs with sorting output.

[codecov]

Codecov Report

Merging #6234 (f72cc27) into master (7ea01d1) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #6234      +/-   ##
==========================================
- Coverage   70.86%   70.83%   -0.04%     
==========================================
  Files         485      487       +2     
  Lines       21951    22053     +102     
==========================================
+ Hits        15556    15621      +65     
- Misses       5397     5425      +28     
- Partials      998     1007       +9     

Impacted Files	Coverage Δ
pkg/skaffold/build/cache/retrieve.go	64.40% <100.00%> (+0.30%)	⬆️
...g/skaffold/kubernetes/portforward/entry_manager.go	91.78% <100.00%> (+0.11%)	⬆️
pkg/skaffold/kubernetes/status/status_check.go	52.40% <100.00%> (+0.51%)	⬆️
pkg/skaffold/runner/build.go	74.28% <100.00%> (+0.24%)	⬆️
pkg/skaffold/sync/sync.go	65.77% <0.00%> (-7.44%)	⬇️
pkg/skaffold/hooks/container.go	66.66% <0.00%> (ø)
pkg/skaffold/hooks/sync.go	85.71% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ea01d1...f72cc27. Read the comment docs.

[tejal29]

We should think about adding an integration test for v2 events api for a sample app like microservices.