AbortedTransactionTest may need to be deleted with duckdb v1.5

[rynoV]

The AbortedTransactionTest relies on the behaviour fixed in duckdb/duckdb#20119, which caused the transaction COMMIT to throw an error, and I don't know of another way to make the transaction COMMIT throw an error. That PR I believe is scheduled for release with 1.5, so when updating to 1.5 the test might start failing and it may be best to just delete it or skip it.

[rynoV]

I don't know of another way to make the transaction COMMIT throw an error

It is possible to cause the transaction to abort (for example by setting the memory_limit very low and running a query), but the test specifically needs the transaction commit to fail after the transaction's statements have run successfully, and I'm not sure of a way to do that