Add tag filtering to invoiceTags list utility

[Kingsman-99]

Description

src/lib/invoiceTags.ts manages tags on invoices but provides no utility to filter a list of invoices by one or more tags. Callers implement this filter ad-hoc in multiple places, leading to inconsistent behaviour when an invoice has multiple tags.

Acceptance Criteria

• filterByTags(invoices: Invoice[], tags: string[], opts?: { matchAll?: boolean }): Invoice[] exported from src/lib/invoiceTags.ts
• Default (matchAll: false): returns invoices that have any of the given tags
• matchAll: true: returns only invoices that have all of the given tags
• Empty tags array returns all invoices unchanged
• Exported from the existing barrel export if one exists
• Unit tests: any-match, all-match, empty tags returns all, no matches returns empty array

Context

• Target file: src/lib/invoiceTags.ts
• Invoice type from src/lib/types — use existing import pattern in the file

[Ranjeet2063]

Hi @maintainers, I am ready to resolve this!

Execution Plan for Add tag filtering to invoiceTags list utility:

• Clean Implementation: Deliver an idiomatic solution for Add tag filtering to invoiceTags list utility adhering strictly to Stellar-split/split-app's architecture.
• Automated Tests: Provide full test coverage asserting both edge cases and core workflows.
• Clean Git Hygiene: Atomic conventional commits with zero merge conflicts.

Why assign me?

• Proven Proof-of-Work: Implement real-time PaymentProgress updates #1 contributor on Mova Store (28 merged Web3 PRs) and official ElizaOS contributor.
• Fast Turnaround: Dedicated to shipping a tested, production-grade PR within 12–24 hours.
• Zero Maintainer Burden: Self-documenting code with green CI and tests included so you don't spend time debugging.

Ready to deliver within 12–24h—please feel free to assign it to me!

[ZacLou]

I reviewed the issue and the existing invoiceTags.ts contract. I would add a small, typed filterByTags helper with any/all matching semantics, preserve the empty-tags behavior, expose it through any existing barrel export, and add focused unit tests for any-match, all-match, empty tags, and no-match cases. I’ll keep the change bounded to this utility and its tests, then run lint/typecheck/tests before submitting the PR after assignment.