chore(deps): bump p-retry from 4.6.2 to 8.0.0 in /packages/webhook

[dependabot]

Bumps p-retry from 4.6.2 to 8.0.0.

Release notes

Sourced from p-retry's releases.

v8.0.0

Breaking

• Require Node.js 22 85cdece
• Change retry callback order 616306e
  • Callback order changed from onFailedAttempt → shouldConsumeRetry → shouldRetry to shouldConsumeRetry → onFailedAttempt → shouldRetry.
  • Consumption decisions are now made before failure notifications and retry decisions.

Improvements

• Add retryDelay to onFailedAttempt context (#66) 96cce98
• Fix TypeError retry handling f011d2e
• Harden retry timing and callback validation 9d47b60

---

sindresorhus/p-retry@v7.1.1...v8.0.0

v7.1.1

• Fix delayed abort when signal is already aborted before delay phase 2aba573

---

sindresorhus/p-retry@v7.1.0...v7.1.1

v7.1.0

• Add shouldConsumeRetry option (#96) 26d6e05

---

sindresorhus/p-retry@v7.0.0...v7.1.0

v7.0.0

Breaking

• Require Node.js 20 3bdb53a
• onFailedAttempt and shouldRetry now receive a context object instead of a decorated error bff36bb
  • You must now must access the error as object.error instead of object.
  • The use of .attemptNumber and .retriesLeft did not change.
• Remove the forever option (#79) 6a89827
  • Many use-cases can use {retries: Infinity} instead for infinite retries.

Improvements

• Rewrite the package to not depend on the retry package (#79) 6a89827
  • This is a full rewrite, so test carefully.
• Add makeRetriable method 1a81c1e

---

... (truncated)

Commits

• 35681f6 8.0.0
• 9d47b60 Harden retry timing and callback validation
• f011d2e Fix TypeError retry handling
• 85cdece Require Node.js 22
• 616306e Change retry callback order
• 96cce98 Add retryDelay to onFailedAttempt context
• 0b1e298 7.1.1
• 2aba573 Fix delayed abort when signal is already aborted before delay phase
• 6ac326b Minor tweak
• 043395a 7.1.0
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 71adc5d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.13%. Comparing base (16bf84c) to head (71adc5d).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2655      +/-   ##
==========================================
- Coverage   89.17%   89.13%   -0.04%     
==========================================
  Files          65       65              
  Lines       10339    10339              
  Branches      474      472       -2     
==========================================
- Hits         9220     9216       -4     
- Misses       1091     1095       +4     
  Partials       28       28              

Flag	Coverage Δ
cli-hooks	89.13% <ø> (-0.04%)	⬇️
cli-test	89.13% <ø> (-0.04%)	⬇️
logger	89.13% <ø> (-0.04%)	⬇️
oauth	89.13% <ø> (-0.04%)	⬇️
socket-mode	89.13% <ø> (-0.04%)	⬇️
web-api	89.13% <ø> (-0.04%)	⬇️
webhook	89.13% <ø> (-0.04%)	⬇️

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[WilliamBergamin]

@dependabot recreate