Gossip propagation issues and gossip map uncompleted

I am not sure why I am the first to report this, but with the [ocean node](https://mempool.space/lightning/node/029ef2ce43571727104099576c633b2233bfeb8dc18b476f93540a32207da9e9a4) where we are running an old but stable release of Core Lightning, version v24.05. However, looks like the gossip is pretty unreliable (much worse that the well-known 'unreliable' behaviour of gossip in Lightning).

As you can see from the mempool site, our node's last update was 5 months ago, but this is not possible because we are paying miners once a day.

I am pretty sure that this issue also occurs with the most recent version because most users of Ocean are using the Start9/Umbrel package, so they are running either the latest version or just one version older.

## Problem Statement

Ocean uses BOLT12 (without a blinded path) for every miner to dispatch the payouts. Some users have the following setup:

```
Ocean Node -> Exit Node (no LSP) -> ... <-> Random Node <-> Miner Node
```

In this case, the miner has a single channel and relies on it for liquidity. At this point, some miners (who have been in the network for a while and have been mining from Ocean and running a Lightning node since last year) are not able to receive payments anymore because our node cannot connect directly to the miner node (our gossip map does not contain the miner’s address because CLN drops it at some point).

To solve this problem, we tell the miner to connect with our node, but this is a hack, and we think that this issue with gossip can also degrade the `pay` performance with some nodes that are not ‘well known’.

This issue is also noted by other implementation like ldk [Gossip never seems to get a full take from Eclair/CLN](https://github.com/lightningdevkit/rust-lightning/issues/3075)

P.S: I could not try with a recent version of CLN there is this issue https://github.com/ElementsProject/lightning/issues/7972 that worries me about upgrading.