test: prove the declined confirmation deleted nothing

The case asserted the abort message and stopped there, so it would have
passed had the delete gone out anyway. Answering the prompt with y now fails
it, which is what "nothing deleted" is supposed to mean.

beep boop

Author: khvn26

internal/cmd/testdata/script/confirm.txtar

@@ -4,11 +4,13 @@
 
 # Given: FLAGSMITH_NO_INPUT set to a falsey value, and a terminal to prompt on
 # When: a destructive command runs and the confirmation is declined
-# Then: the prompt still ran — a falsey value switches the behaviour off rather than merely being set
+# Then: the prompt still ran, and declining it deleted nothing — a falsey value switches the behaviour off rather than merely being set
 env FLAGSMITH_NO_INPUT=false
 ttyin -stdin decline
 exec flagsmith project delete 101
 stderr 'Aborted; nothing deleted\.'
+dump requests requests.txt
+! grep 'DELETE /api/v1/projects/101/' requests.txt
 env FLAGSMITH_NO_INPUT=
 
 -- flagsmith.json --