Ask Orders doesn't settle

**Expected behavior**
After submitted an "Ask" order (Sell channel), it should automatically open a channel to the selected node.

**Actual behavior**
After submitted an "Ask" order (Sell channel), the order is blocked on the "ORDER_SUBMITTED" state for several days, with the following details:
```
{
"asks": [
{
"details": {
"trader_key": "XXXXX",
"rate_fixed": 694,
"amt": "10000000",
"max_batch_fee_rate_sat_per_kw": "12500",
"order_nonce": "XXXXX",
"state": "ORDER_SUBMITTED",
"units": 100,
"units_unfulfilled": 100,
"reserved_value_sat": "10002135",
"creation_timestamp_ns": "1707304700838378803",
"events": [
{
"timestamp_ns": "1707304700838378803",
"event_str": "OrderCreated"
}
],
"min_units_match": 100,
"channel_type": "ORDER_CHANNEL_TYPE_PEER_DEPENDENT",
"allowed_node_ids": [
"XXXXX"
],
"not_allowed_node_ids": [],
"auction_type": "AUCTION_TYPE_BTC_INBOUND_LIQUIDITY",
"is_public": true
},
"lease_duration_blocks": 2016,
"version": 5,
"announcement_constraints": "ANNOUNCEMENT_NO_PREFERENCE",
"confirmation_constraints": "CONFIRMATION_NO_PREFERENCE"
}
],
"bids": []
}
```

**To reproduce**

**System information**

I'm using Pool as part of Lightning Terminal.

Start with Lightning Pool’s Ask-order submission and ORDER_SUBMITTED state handling, using the reported order details as the reproduction context. Check Pool logs and the Lightning Terminal integration while reproducing; done means determining why the order remains blocked and verifying that an Ask order can automatically open a channel to the selected node.

Written by the indexing model from the issue text.