feat(ipns): server-side name search on ListKeys

[pcfreak30]

Adds server-side name search to IPNS key listing, matching the request-editor pattern already used by portal-sdk.

The portal /api/ipns/keys endpoint is a queryutil list endpoint supporting filters[name][contains] for name substring search. The ipfs-sdk ListKeys ignored this, so name search would have to be client-side. Now it runs server-side.

Changes:

• ListKeyOption with WithFilterName(name): threads filters[name][contains]= onto the list request query via a request editor.
• ListKeys(ctx, opts ...ListKeyOption) preserves the no-filters call path unchanged for existing callers (no editor when empty).
• Generated IPNSService mock updated to the variadic signature.

End-to-end test asserts the contains filter is actually sent server-side and that a plain ListKeys sends no filter. Wiring mutation-verified. All ipfs-sdk tests pass.

---

Summary

This PR adds server-side name search capability to the IPNS key listing functionality (ListKeys).

Changes

API Enhancement

• ListKeys now accepts optional ListKeyOption parameters, enabling callers to filter IPNS keys by name.
• A new ListKeyOption type with a WithFilterName(name string) method was introduced, allowing callers to narrow results to keys whose names contain a given substring.

Server-Side Filtering

• When a name filter is provided, the SDK sends a filters[name][contains]=<name> query parameter to the portal's /api/ipns/keys endpoint.
• This filtering is performed server-side by the portal, not by fetching all keys and filtering client-side, improving efficiency for large key lists.
• Without a filter, the call behaves exactly as before, preserving backward compatibility for existing callers and tests.

Supporting Changes

• The IPNSService interface signature was updated to accept variadic ListKeyOption parameters.
• Mock implementations were regenerated to match the updated interface.
• Added an end-to-end test verifying that:
  • A filtered ListKeys call sends the correct filters[name][contains] query parameter.
  • A plain ListKeys call sends no filters.

No portal-side changes are required since the endpoint already supports queryutil list-query filtering.

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[github-actions]

Code Coverage Report

Total Coverage: 11.2%

Generated from commit: 6ccf2fc
Repository: LumeWeb/ipfs-sdk