[bug]: provide more details on the new RBF cooperative close feature in release notes

[ZZiigguurraatt]

In the latest release notes, we have

lnd/docs/release-notes/release-notes-0.19.0.md

Lines 133 to 147 in b34afa3

	* `lnd` now [supports the new RBF cooperative close
	flow](https://github.com/lightningnetwork/lnd/pull/9610). Unlike the old
	flow, this version now uses RBF to enable either side to increase their fee
	rate using their _own_ channel funds. This removes the old "negotiation"
	logic that could fail, with a version where either side can increase the fee
	on their coop close transaction using their channel balance.
	This new feature can be activated with a new config flag:
	`--protocol.rbf-coop-close`.
	With this new co-op close type, users can issue multiple `lncli closechannnel`
	commands with increasing fee rates to use RBF to bump an existing signed co-op
	close transaction.

which links to a PR that has no description and a bunch of commits.

This is a big and powerful change that I think we should more clearly explain to users in english what is going on and what it is compatible with.

Some key points that I think we should mention:

• This uses the new protocol defined at https://github.com/lightning/bolts/pull/1205/files which is called option_simple_close. Channel peers must support option_simple_close for this new protocol to work.
• It is not compatible with older LND versions, closing channels with channel peers that use older LND versions must use CPFP still to increase the effective fee.
• It should work with peers running eclair version 0.12.0 and greater.
• LDK does not seem to have implemented option_simple_close (Implement new simple coop close lightningdevkit/rust-lightning#2433), so it will not work with channel peers running any current version of LDK.
• CLN does not seem to have any documentation regarding option_simple_close, so it likely does not work with channel peers running CLN.

[ZZiigguurraatt]

which links to a PR

https://bitcoinops.org/en/newsletters/2025/03/28/#lnd-8453 also mentions a number of additional PR related to this feature. Are these PR also relevant and worth mentioning or is Bitcoin Optech wrong?

[ZZiigguurraatt]

We also need to make it clear that it does not work in the following situations:

1. taproot channels ([feature]: add taproot chan support to rbf-closer #9662)
2. custom channels ([feature]: add custom chan support to new rbf chan closer #9663)