chore(deps): update dependency find-up to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
find-up	7.0.0 → 8.0.0

---

Release Notes

sindresorhus/find-up (find-up)

v8.0.0

Compare Source

Breaking

• Require Node.js 20 321107b
• Stop re-exporting path-exists (#​69) d65d145
  • import it directly from its package.

Improvements

• Add {type: 'both'} option to find files or directories 67f453c
• Add findDown and findDownSync to search descendant directories 8e02916

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• 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.

[doistbot]

This PR bumps the find-up devDependency from 7.0.0 to 8.0.0 — a straightforward update since the package isn't imported anywhere in the source.

Few things worth tightening:

• The lockfile wasn't regenerated, so package-lock.json still pins find-up at 7.0.0 while package.json declares 8.0.0. Run npm install and commit the updated package-lock.json — otherwise npm ci will fail in CI.

_{Share Feedback • Review Logs}

[doistbot]

The lockfile wasn't updated for this bump. package-lock.json still lists "find-up": "7.0.0" in the root devDependencies and node_modules/find-up is still resolved to 7.0.0, while package.json now declares 8.0.0. With this mismatch, npm ci fails during install, and npm install won't actually pull v8. Run npm install to regenerate the lockfile and commit the updated package-lock.json along with this change.