feat: wait for actions using ActionsClient.wait_for

[jooola]

This function allows the users to wait for multiple actions in an efficient way. All actions are queried using a single call, which reduce the potential for running into rate limits.

[codecov]

Codecov Report

Attention: Patch coverage is 95.89041% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.48%. Comparing base (be61f7f) to head (6bf2b5d).

Files with missing lines	Patch %	Lines
hcloud/actions/client.py	92.30%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #508      +/-   ##
==========================================
+ Coverage   93.43%   93.48%   +0.04%     
==========================================
  Files          64       65       +1     
  Lines        3048     3115      +67     
==========================================
+ Hits         2848     2912      +64     
- Misses        200      203       +3     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[apricote]

This hides/ignores any errors for actions that already completed. Should they be included in the Exception or should users that want this behavior pass their own handle_update callable and track these action errors themselves?

[jooola]

Not entirely sure about this one.

I doubt there is a use case for having the actions that succeeded, we are more focused on the actions that timeout.

I think usage will tell, so I'll start using this in the ansible collection and see how this works out.

[apricote]

Sorry, I was not clear enough. Besides the actions that time out, maybe the user is also interested in the actions that errored, to show a full picture of the issues.