fix(types): correct invoice log param and utilityPayment id type

[mateussiqueira]

Description

Two TypeScript type definition fixes found while reviewing the SDK.

1. invoice.log.query() and invoice.log.page() use wrong param name (#114)

The type definitions use paymentIds in the function signature, but the JS runtime destructures invoiceIds. TypeScript users passing paymentIds would have their filter silently ignored — the value goes nowhere.

The JSDoc @param already correctly says invoiceIds, so this was a copy-paste mistake from other payment-type log modules (which correctly use paymentIds for their domain).

2. UtilityPayment.id should not be optional (#113)

// Before:
readonly id?: string | null

// After:
readonly id: string

The id is always returned by the API for existing payments. Having it as string | null | undefined forces unnecessary null checks on users who retrieve payments. The constructor still accepts id?: string | null for creation scenarios.

Testing

• No runtime changes — only TypeScript type definitions were updated
• npm test (mocha) passes
• npm run test:typescript (jest) passes

Closes #113
Closes #114

[mateussiqueira]

Follow-up: algum feedback sobre este PR? Corrige os tipos de invoice log (paymentIds → invoiceIds) e torna UtilityPayment.id obrigatório.

Esses bugs de tipo afetam usuários TypeScript que usam strict mode.