CoreLN not properly detecting force close UTXOs

### Issue and Steps to Reproduce

I have a CoreLN node running 23.08. I was trying to track down a Force Close we had and where the funds had gone because I didn't notice them in my onchain wallet. I looked at the transactions in a block explorer and saw that they ended up in a particular address, but that address wasn't listed in my `listfunds` output. To ensure this address actually belonged to me I searched for the address in the `dev-listaddrs` command's output. The address showed up in that output so it seemed to me that my CoreLN node did own the address, however these funds were not showing up in the wallet. So I figured I needed to rescan the wallet to find the funds.

Before I did anything, I check all my UTXOs in the `listfunds` command and I had **15** UTXOs. They were a mix of `confirmed` and `unconfirmed` and a few were `reserved`. I first tried the `dev-rescan-outputs` command. This ran successfully but it decreased my UTXOs to **7**. So I figured that didn't completely do what I wanted it to. Next I tried to do a `rescan` in the config and set it to a specific block height that was just before this force close transaction. After the rescan finished `listfunds` had **71** UTXOs which are all confirmed. Once I started looking into all these new UTXOs, I noticed they were all from force closes over time.

I can provide whatever technical details necessary for debugging, but it seems like CoreLN is not tracking these UTXOs properly. Thanks.