chore(deps): update dependency dev.openfeature.contrib.providers:flagd to v0.5.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dev.openfeature.contrib.providers:flagd (source)	0.5.0 -> 0.5.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov-commenter]

Codecov Report

Merging #181 (c38f1bf) into main (1a40c97) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #181   +/-   ##
=========================================
  Coverage     91.60%   91.60%           
  Complexity      187      187           
=========================================
  Files            20       20           
  Lines           417      417           
  Branches         22       22           
=========================================
  Hits            382      382           
  Misses           23       23           
  Partials         12       12           

Flag	Coverage Δ
unittests	91.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[toddbaert]

FYI with this version of flagd we introduce some default timeouts that are occaisionally being hit on test runs. I've set the timeout more generously in the integration suite to resolve this.