fix(notifications): handling for payments and channel opening

[pwltr]

Description

• Ensure LSP peer connection before opening channel in .orderPaymentConfirmed
• Match payment hash in .paymentReceived to prevent wrong payment notifications
• Add activity item and .receivedTx sheet for CJIT payments
• Clean up commented code and unused variables

[Copilot]

Pull request overview

This PR improves notification handling for Lightning payments and channel operations by ensuring proper LSP peer connections and payment validation. The changes fix potential issues where notifications could be shown for incorrect payments or channels could fail to open due to missing peer connections.

Key Changes:

• Add LSP peer connection validation before channel opening operations
• Implement payment hash matching to prevent wrong payment notifications
• Add activity tracking and UI sheet display for CJIT payments

Reviewed changes

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

File	Description
BitkitNotification/NotificationService.swift	Adds peer connection handling, payment hash validation, CJIT activity tracking, and cleans up unused code
Bitkit/ViewModels/AppViewModel.swift	Adds receivedTx sheet display for CJIT payments

[jvsena42]

value displayed on CJIT sheet matches the outbound ✅
couldn't test the notification