chore(deps): update dependency @openfeature/web-sdk to v1 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@openfeature/web-sdk	^0.4.0 -> ^1.0.0
@openfeature/web-sdk	^0.4.0 -> ^0.4.0 || ^1.0.0

---

Release Notes

open-feature/js-sdk (@​openfeature/web-sdk)

v1.0.0

Compare Source

Miscellaneous Chores

• release 1.0.0 (930f754)

---

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 these updates 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.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: js-sdk-contrib@0.0.0
npm ERR! Found: @openfeature/core@0.0.21
npm ERR! node_modules/@openfeature/core
npm ERR!   dev @openfeature/core@"^0.0.21" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @openfeature/core@"1.0.0" from @openfeature/web-sdk@1.0.0
npm ERR! node_modules/@openfeature/web-sdk
npm ERR!   dev @openfeature/web-sdk@"^1.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-15T16_07_22_506Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-15T16_07_22_506Z-debug-0.log

[thomaspoignant]

For this PR to be mergeable we need to update the @openfeature/core dependency at the same time.