[Routing Saga]: Limit route contstruction and invoice clearing over payment channel settlement

[dstadulis]

The tapd daemon's logic for constructiong routes and clearing HTLC state needs to be tailored tighter to expectations when generating invoices. This lack of specificity leads to several issues related to how the daemon views payment bandwidth and settles HTLCs.

Related Issues:

• tapchannel/[feature]: update AuxInvoiceManager to enforce strict forwarding for invoices #1008
• [custom channels]: fix bandwidth reported by TLV traffic shaper #1060

• [Continue to add other issues]

Solution:

A more robust solution is needed to ensure the tapd daemon can handle HTLCS for invoices with custom data. This may involve changes to how the daemon selects and clears payment-channel state, as well as how it settles HTLCS.