chore: unleash integration test stability issues

[toddbaert]

This fails sometimes when CI is busy.

[gemini-code-assist]

Code Review

This pull request introduces a polling mechanism to ensure feature flags are fully propagated to the Unleash client API before integration tests proceed, which helps prevent flakiness. A review comment suggests improving error handling in the polling loop by catching specific network exceptions instead of a broad exception.

[gemini-code-assist]

Catching a broad Exception can hide unexpected issues and make debugging harder. It's generally better to catch more specific exceptions. For network-related issues during polling, requests.exceptions.RequestException is more appropriate.

Suggested change

	except Exception as e:
	except requests.exceptions.RequestException as e:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.72%. Comparing base (7e18bc1) to head (b7e8762).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
+ Coverage   90.16%   98.72%   +8.56%     
==========================================
  Files           1        3       +2     
  Lines         122      157      +35     
==========================================
+ Hits          110      155      +45     
+ Misses         12        2      -10     

☔ 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.