chore(deps): update dependency @frontify/eslint-config-react to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@frontify/eslint-config-react (source)	^0.17.7 → ^1.0.0

---

Configuration

📅 Schedule: (in timezone Europe/Zurich)

• Branch creation
  • "after 9pm,before 6am"
• 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 was generated by Mend Renovate. View the repository job log.

[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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: typeform_block@1.0.0
npm error Found: eslint@8.57.1
npm error node_modules/eslint
npm error   dev eslint@"^8.57.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^9.0.0 || ^10.0.0" from @frontify/eslint-config-react@1.0.16
npm error node_modules/@frontify/eslint-config-react
npm error   dev @frontify/eslint-config-react@"^1.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-17T12_34_43_318Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-17T12_34_43_318Z-debug-0.log