fix(replication): replace custom AbortToken with tokio::CancellationToken

[meskill]

Replace custom AbortSignal with CancellationToken to make the cancellation explicit and not relied on futures drop (that holds rx part of channel). Pass cancellation token for graceful cancellation. Early cancellation on errors

[codecov]

Codecov Report

❌ Patch coverage is 43.39623% with 30 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...end/replication/logical/publisher/parallel_sync.rs	0.00%	13 Missing ⚠️
...nd/replication/logical/publisher/publisher_impl.rs	76.66%	7 Missing ⚠️
...og/src/backend/replication/logical/orchestrator.rs	0.00%	5 Missing ⚠️
pgdog/src/api/copy_data.rs	0.00%	3 Missing ⚠️
...src/backend/replication/logical/publisher/table.rs	0.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[sgrif]

Suggested change

	// If every handle succeed the guard token will just cancel already finished work
	// If every handle succeeds the guard token will just cancel already finished work

[sgrif]

I think we should require the caller to call .child_token() if they don't want to be cancelled.

Suggested change

let cancel = cancel.child_token();

[sgrif]

Suggested change

	let _guard = cancel.clone().drop_guard();
	let _guard = cancel.drop_guard_ref();

[sgrif]

Suggested change

	let cancel = cancel.clone();
	syncs.push(async move {
	let manager = ParallelSyncManager::new(tables, replicas, dest)?;
	let tables = manager.run().await?;
	let tables = manager.run(cancel).await?;
	syncs.push(async move {
	let manager = ParallelSyncManager::new(tables, replicas, dest)?;
	let tables = manager.run(cancel.child_token()).await?;

[sgrif]

This is the first place we actually do anything with a cancellation token other than pass it through. Should we remove everything up the chain from here and the CancellationToken::new()s, and create it at this point?