feat: allow not waiting for actions

[phm07]

This PR adds the no-wait option, which allows to skip waiting for actions.

Closes #833

Related to #613, #489, #284

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 11 lines in your changes missing coverage. Please review.

Project coverage is 61.35%. Comparing base (f7c9ac6) to head (1b3d7dd).
Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/state/actions.go	0.00%	9 Missing ⚠️
internal/ui/actions.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #843      +/-   ##
==========================================
- Coverage   61.43%   61.35%   -0.08%     
==========================================
  Files         237      237              
  Lines        8494     8505      +11     
==========================================
  Hits         5218     5218              
- Misses       2567     2578      +11     
  Partials      709      709              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[apricote]

Do we have "composite" commands in the CLI, where we wait for some actions and then make more API calls? These could fail if we do not wait for the initial actions.

[phm07]

Yes, for example when enabling protection after resource creation. How about we add a function like MustWaitForActions which doesn't include the wait option logic and then make WaitForActions a wrapper of that?

[apricote]

Sounds fine to me.

We should also look at these cases and decide if its really necessary to wait for the running actions or the next call is independent and can still be made. (ie. is it necessary for the server to start before enabling the protection?)

[phm07]

Since the scope of this PR is bigger than expected, I will close it for now. We plan to revisit this idea later.