chore: update deps and bump to v0.0.3

[lidel]

Dependency update ahead of the next release:

• boxo v0.42.1
• go-libp2p-kad-dht v0.42.1
• go-libp2p v0.49.0, which pulls webtransport-go v0.11.1 with the fix for CVE-2026-57497 (memory exhaustion from buffered unknown capsules)

kad-dht v0.42.0 dropped the lifecycle context from its constructors, so the dht.New call in lib/dht_test.go loses its ctx argument. That is the only code change the updates needed, so just shipping as-is.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 24.47%. Comparing base (a30a0de) to head (7a58e5e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #66   +/-   ##
=======================================
  Coverage   24.47%   24.47%           
=======================================
  Files           7        7           
  Lines         568      568           
=======================================
  Hits          139      139           
  Misses        390      390           
  Partials       39       39           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Suggested tag: v0.0.3

Comparing to: v0.0.2 (diff)

gorelease says:

# summary
v0.0.3 is a valid semantic version for this release.

gocompat says:

HEAD is now at a30a0de Merge pull request #65 from ipshipyard/new-version
Switched to branch 'main'
Your branch is up to date with 'origin/main'.

Cutting a Release (and modifying code files)

This PR is modifying both version.json and code files (not markdown, YAML, TOML or lock files).
The Release Checker is not able to analyse files that are not checked in to main. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.