min-emergency-msat requirement even with zero channels open

### Issue and Steps to Reproduce

### `getinfo` output
```
~/.lightning$ lightning-cli getinfo
{
"id": "033db47ac0c48fdcc94b7662852e740916d5ad79ee1bdebddd13bfeedc1dab3e04",
"alias": "YELLOWWAFFLE",
"color": "033db4",
"num_peers": 1,
"num_pending_channels": 0,
"num_active_channels": 0,
"num_inactive_channels": 1,
"address": [],
"binding": [
{
"type": "ipv6",
"address": "::",
"port": 9735
},
{
"type": "ipv4",
"address": "0.0.0.0",
"port": 9735
}
],
"version": "v24.02.2",
"blockheight": 842888,
"network": "bitcoin",
"fees_collected_msat": 0,
"lightning-dir": "/home/ubuntu/.lightning/bitcoin",
"our_features": {
"init": "08a0800a8a59a1",
"node": "88a0800a8a59a1",
"channel": "",
"invoice": "02000002024100"
}
}
```

### Steps to reproduce:
- Spin up 2 core LN nodes.
- send 250k sat utxo to 1 node.
- setup a channel for roughly 222k sats between them. (minus fees and forces me to keep a reserve 25k sat utxo)?
- make bolt 12 payments / offers but not enough to justify a utxo on the receivers side.
- mutual close.
- try `withdraw` addr amount -> get errors about `min-emergency-msat` try setting min-emergency-msat to 0 but needs to be over dust limit.
- set config to 546 and do a withdraw.
- pollute utxo set with dust.

Note:
- `"num_inactive_channels": 1,`

#### Might be related: (But I think this is when channels are still open)?
https://github.com/ElementsProject/lightning/issues/7131

Beginne damit, das Zwei-Knoten-Setup zu reproduzieren und die Withdraw-Verarbeitung für einen Knoten mit null aktiven, aber einem inaktiven Kanal nachzuverfolgen, wobei der Fokus auf der Validierung von min-emergency-msat liegt. Vergleiche das Verhalten mit dem verwandten Issue #7131; abgeschlossen ist die Untersuchung, wenn die beabsichtigte Verarbeitung geklärt und die Regression abgedeckt ist, ohne einen Workaround mit einer staubgroßen Auszahlung zu benötigen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.