Update dependency @ipld/dag-cbor to v9.2.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@ipld/dag-cbor	9.2.4 → 9.2.7

---

Release Notes

ipld/js-dag-cbor (@​ipld/dag-cbor)

v9.2.7

Compare Source

Dependencies

• dev: bump aegir from 47.2.0 to 48.0.1 (#​134) (aacbe8d)

v9.2.6

Compare Source

Bug Fixes

• adapt to cborg@​5 changes (b77ee42)

Dependencies

• bump cborg from 4.5.8 to 5.0.0 (fa48f20)

v9.2.5

Compare Source

Bug Fixes

• reject non-string map keys (and zero length keys) (#​130) (ab169ee)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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: pnpm-lock.yaml

[WARN] The "pnpm" field in package.json is no longer read by pnpm. The following keys were ignored: "pnpm.onlyBuiltDependencies", "pnpm.overrides". See https://pnpm.io/settings for the new home of each setting.
Error: ERR_PNPM_MISSING_TARBALL_INTEGRITY

  × updating dependencies
  ╰─▶ 1 lockfile entries failed verification:
        xlsx@https://cdn.sheetjs.com/xlsx-0.19.1/xlsx-0.19.1.tgz has no
      "integrity" field, so its downloaded tarball cannot be verified
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. Alternatively, relax the policy that flagged them.