feat: new exec command to execute a custom action

[renzodavid9]

Fixes: #8628

Description
This PR adds the logic to include the new exec command to execute a Custom Action together with the new v2 events to communicate the state of an exec run.

[codecov]

Codecov Report

Merging #8696 (da83ca4) into main (290280e) will decrease coverage by 6.05%.
The diff coverage is 49.59%.

@@            Coverage Diff             @@
##             main    #8696      +/-   ##
==========================================
- Coverage   70.48%   64.44%   -6.05%     
==========================================
  Files         515      617     +102     
  Lines       23150    31168    +8018     
==========================================
+ Hits        16317    20085    +3768     
- Misses       5776     9577    +3801     
- Partials     1057     1506     +449     

Impacted Files	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 406 files with indirect coverage changes

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

[aaron-prindle]

this tip message "run vs deploy" is likely not correct for the exec command. Should likely be changed to a more appropriate err msg

[renzodavid9]

Done! I added a new tip message explaining how to use images from previous builds. Thanks!

[aaron-prindle]

nit: I believe everytime 2+ actions are run together there will be a warning in stdout that liely shouldn't be there:

WARN[0009] action-succeeded cleanup error:removing stopped container: Error: No such container: 3d3a3398da733805ae819738f9fbce90ef04906ad50e16966681bafe531af372  subtask=-1 task=DevLoop

I think this is related to the docker purge issue we mentioned in the past, forget the status of that

Doesn't have to be addressed here, just wanted to point out this UX issue

[aaron-prindle]

Just tried it out, works great!

[renzodavid9]

nit: I believe everytime 2+ actions are run together there will be a warning in stdout that liely shouldn't be there:

WARN[0009] action-succeeded cleanup error:removing stopped container: Error: No such container: 3d3a3398da733805ae819738f9fbce90ef04906ad50e16966681bafe531af372  subtask=-1 task=DevLoop

I think this is related to the docker purge issue we mentioned in the past, forget the status of that

Doesn't have to be addressed here, just wanted to point out this UX issue

Yes! That's exactly what's happening. I have a branch with the changes to improve this for the custom actions case (renzodavid9/skaffold@ca-feature-8628...renzodavid9:skaffold:ca-issue-prune-err) where I split the docker client logic in another method so we don't run prune. This is to improve the custom actions case, but for a long term solution the idea is to use docker labels to know what to prune. My idea is to create the PR with the changes once this one gets merged.

[aaron-prindle]

LGTM!