feat: upgrade p-queue (no changes)

[FauxFaux]

Summary

p-queue now provides its own types, and @types/p-queue throws a deprecation warning,
so remove it. (I only care about the deprecation warning.)

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #1097 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1097   +/-   ##
=======================================
  Coverage   94.35%   94.35%           
=======================================
  Files          12       12           
  Lines         797      797           
  Branches      177      177           
=======================================
  Hits          752      752           
  Misses         15       15           
  Partials       30       30           

Flag	Coverage Δ
#eventsapi	90.74% <ø> (ø)
#interactivemessages	94.83% <ø> (ø)
#webapi	95.59% <ø> (ø)
#webhook	87.50% <ø> (ø)

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

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cebb85e...2d1e09d. Read the comment docs.

[stevengill]

LGTM. I reviewed the breaking changes on pqueue since the previous major we used. Nothing breaks on our end to upgrade.

Thanks for sending this in!

[aoberoi]

@stevengill how do we verify changes like v6.5.0 don't break anything? specifically, that release updates TypeScript to v3.9, which is above our projects' minimum TypeScript version of v3.3.

i recall that in the past situations where dependencies (especially those that bundle their own type definitions instead of retrieving them from DT) start to use new TypeScript syntax, that effectively bumps our project's minimum TypeScript version, too. but i'm not sure if that was all cases, or only in cases where some part of our project's API was dependent on a type from the dependencies API.

i think, before the changes in #831 for the sdk-integration-tests, we actually had CI verify the compatibility with our oldest supported TypeScript version. i'm not sure the refactored version provides that verification anymore.