simplify-build-failure rm -rf tasks/

If the user runs simplify-build-failure and copies the result back in to the source dir, running simplify-build-failure a second time could make it be confused otherwise

Bug: 132727976
Test: accidentally populate frameworks/support/tasks and then run simplify-build-failure and see that it doesn't try to run the tasks mentioned in that dir

Change-Id: I5c8afa530cf3f23f7f6ac37a0c56e1dd700e4c92
diff --git a/development/simplify-build-failure/simplify-build-failure.sh b/development/simplify-build-failure/simplify-build-failure.sh
index 0ec8470..8a36722 100755
--- a/development/simplify-build-failure/simplify-build-failure.sh
+++ b/development/simplify-build-failure/simplify-build-failure.sh
@@ -190,6 +190,7 @@
   sed -i 's/.*Exception.*cannot include.*//' "$referenceFailingDir/settings.gradle"
   # remove some generated files that we don't want diff-filterer.py to track
   rm -rf "$referenceFailingDir/.gradle" "$referenceFailingDir/buildSrc/.gradle" "$referenceFailingDir/out"
+  rm -rf "$referenceFailingDir/tasks" # generated by simplify-build-failure and could be inadvertently copied into source by the user
 fi
 
 # compute destination state, which is usually empty