fix: don't block purchased channels when geoblocked

[jvsena42]

Description

This PR lets the user use existing blocktank channels even when geoblocked

Testing scenarions:

• User with purchased channels before geo-blocking → Can still use them
• User is geo-blocked with no channels → CJIT onboarding shown, cannot create new channels
• User has ready channels (any type) → Can receive Lightning payments regardless of geo-blocking

Linked Issues/Tasks

Closes #244

Screenshot / Video

geoblocked-cjit.mp4

geoblocked-tranffer-not-displayed.mp4

[Copilot]

Pull request overview

This PR fixes a bug where users with purchased Blocktank channels were incorrectly blocked from using them when geoblocked. The fix simplifies the logic by checking for any ready channels instead of distinguishing between LSP and non-LSP channels.

Key Changes

• Replaced geoblocking logic that prevented usage of Blocktank channels with a simpler check for any ready channels
• Unified the hasUsableChannels logic across receive and invoice creation flows
• Removed unnecessary hasNonLspChannels() method calls in favor of checking isChannelReady status

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Bitkit/Views/Wallets/Receive/ReceiveQr.swift	Simplified hasUsableChannels to check for any ready channels, updated CJIT onboarding logic to use the unified check, and modified geoblocking condition to use hasUsableChannels
Bitkit/ViewModels/WalletViewModel.swift	Replaced complex geoblocking channel check with simple isChannelReady verification for invoice creation

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[jvsena42]

waiting staging nodes to run again