fix(deps): update dependency tollbooth-dpyc to v0.90.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
tollbooth-dpyc	==0.89.1 → ==0.90.0

---

Release Notes

lonniev/tollbooth-dpyc (tollbooth-dpyc)

v0.90.0

Compare Source

Added — the operator can see its own Lightning balance, and spend it

Every BTCPay call in this SDK was about taking sats IN. create_payout was the
one exception and it has no call site anywhere in the fleet, because a store
payout lands in AwaitingApproval and needs a configured processor before it
moves — which is a queue, not a payment. Two Greenfield endpoints that do move
money are now wrapped:

• BTCPayClient.get_lightning_balance() — GET /stores/{id}/lightning/{crypto}/balance,
  normalised to satoshis throughout, which the API is not. BTCPay reports
  off-chain amounts in millisatoshi and on-chain amounts in satoshi, both as
  strings, in a single response object. A caller reading offchain.local as
  sats is wrong by a factor of a thousand in the direction that says a nearly
  empty node is richly funded. sendable_sats is the local end of active
  channels — the only balance a Lightning payment can draw on. Null and empty
  amounts read as zero rather than raising: a balance check that throws stops a
  payout for the wrong reason. Needs btcpay.store.canuselightningnode.

• BTCPayClient.pay_lightning_invoice() — POST /stores/{id}/lightning/{crypto}/invoices/pay.
  Both fee limits are required arguments, not defaults: a routing fee is
  charged on top of the invoice, so a payment always costs more than it pays,
  and an unbounded one is unbounded. The body is returned as it came back,
  including on 202, which means the payment is under way and not that it
  settled — treating "initiated" as "paid" is how a payment gets sent twice.
  Needs btcpay.store.cancreatelightninginvoice.

Neither is called by the SDK itself. They exist so an operator paying a winner
or a charity does not have to reach past BTCPayClient and integrate with
BTCPay directly.

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[dpyc-agentic-desk]

✅ Deploy verified live: version 0.8.6, serving 04a8f451 (matches the merge).