Update to bitcoin:0.32

[bennyhodl]

All peer dependencies are now able to update to bitcoin 32.

Most changes are renaming of methods and different export paths.

Notable changes:

• lightning no longer exports std::io::Cursor and uses an emulation through lightning::io::Cursor. PR lightning/src/io/mod.rs
• New methods to the lightning peer manager peer_connected and peer_disconnected. I believe they don't do anything since there is no specific node feature flagging for DLC's. Which could be an interesting feature to add to assert peers are able to parse DLC mesages.
• When parsing network related information for writing addresses in the messenger, we can no longer parse the network since it is not public on the address. Since non-mainnet addresses are parsed the same we can only check if the network is mainnet or a testnet flavor. Not sure if we can pass a network here.
• bitcoin 32 introduces using Amount over u64 in all transaction related structs. I opted to keep this crate as u64 but I think should introduce using Amount over u64 in a future PR.

[bennyhodl]

create_cet_adaptor_sig_is_valid is failing. Couldn't track down why.

[Tibo-lg]

That's nice thanks! I couldn't see right away what could be the issue with the unit test that is failing, but it might be good to try to get the integration tests running to see if it's really just that unit test or if there is an actual issue (not sure what is the issue with them, seems something to do with coin selection).

[bennyhodl]

@Tibo-lg coin selection seems to be the issue for integration tests. Doesn't seem to lead to the unit test though.

Integration tests are very flakey so haven't gotten them to fully pass.

How should we handle the derivation index and conf time? Not sure if it should be included with the Utxo type.

[Tibo-lg]

I don't think it matters because these fields are probably used by BDK but not in these tests. I tried running the integration tests by replacing BnB with OlderFirst, but it then runs into a signature verification error which might be the same issue highlighted by the failing unit test. I'll try to look a bit more what could be the issue but it's not obvious for now.

[Tibo-lg]

I think I've fixed all issues. I wanted to push to your branch but was somehow not able not sure why. Can you cherry pick this commit? be327ce
Then have a look to make sure the changes make sense to you. I'll have a last look tomorrow and if everything is good will merge.

[bennyhodl]

tACK

rebased and pushed with the changes.

Looks like the issue was the hash type macro?

[bennyhodl]

Is this good to merge and release?

[Tibo-lg]

Is this good to merge and release?

No CI is not passing, it seems there is some PSBT issue. I don't have time to look at it right now, I'll try to next week, but if you solve it before I'm happy to make a release
https://github.com/p2pderivatives/rust-dlc/actions/runs/10863236537/job/30147194064?pr=234#step:7:13

[Tibo-lg]

This should fix the error.

Suggested change

	let transaction = fund_psbt.extract_tx().map_err(|e| {
	Error::InvalidState(format!(
	"Could not extract transaction from funding psbt. {}",
	e
	))
	})?;
	let transaction = fund_psbt.extract_tx_unchecked_fee_rate();

[bennyhodl]

Thank you. Pushed the change and all pass.