Bump the npm_and_yarn group across 2 directories with 3 updates

[dependabot[bot]]

Bumps the npm_and_yarn group with 2 updates in the /api/javascript/gha-cleanup directory: cross-spawn and @octokit/rest. Bumps the npm_and_yarn group with 1 update in the /graphql/enterprise directory: dset.

Removes cross-spawn

Updates @octokit/rest from 16.39.0 to 21.0.2

Release notes

Sourced from @​octokit/rest's releases.

v21.0.2

21.0.2 (2024-08-16)

Bug Fixes

• docs: update to react 18 and latest gatsby deps (#462) (9a80f06), closes #216 #230 #460

v21.0.1

21.0.1 (2024-07-17)

Bug Fixes

• update deps (#456) (93d5afb)

v21.0.0

21.0.0 (2024-06-20)

Features

• v21 (#413) (12b6c65)

BREAKING CHANGES

• package is now ESM

v21.0.0-beta.4

21.0.0-beta.4 (2024-06-19)

Bug Fixes

• update REST endpoints (#428) (7058346)

v21.0.0-beta.3

21.0.0-beta.3 (2024-04-30)

Features

• security: Add provenance (#420) (9adf1a4)

v21.0.0-beta.2

21.0.0-beta.2 (2024-04-16)

Bug Fixes

... (truncated)

Commits

• 9a80f06 fix(docs): update to react 18 and latest gatsby deps (#462)
• 3b5a8e8 chore(deps): update dependency fetch-mock to v11 (#459)
• 5a4eeb6 test: re-activate more tests and convert them to typescript (#457)
• 93d5afb fix: update deps (#456)
• 5a681c3 chore: use vitest (#450)
• 462e351 ci: start testing against 22 (#447)
• 09bfea8 chore(deps): update dependency glob to v11 (#445)
• 969d6dc chore(deps): update dependency esbuild to ^0.23.0
• 239b1be chore(deps): update dependency esbuild to ^0.22.0
• cdbf93a ci(action): update actions/add-to-project action to v1.0.2
• Additional commits viewable in compare view

Updates dset from 3.1.2 to 3.1.4

Release notes

Sourced from dset's releases.

v3.1.3

Patches

• Add "types" export conditions for TypeScript "nodenext"/"node16" resolution: #40 Thank you @​Akkuma

---

Full Changelog: https://github.com/lukeed/dset/compare/v3.1.2...v3.1.3

Commits

• 05b1ec0 3.1.4
• 16d6154 fix: prevent proto assignment via implicit string
• 48f14a1 3.1.3
• aca90fb chore: add "types" conditions for TS "nodenext" resolution (#40)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.