acc: stop bundle-generate tests leaking cloud workspace dirs (#5946)

## Why

Several `bundle/generate` acceptance tests create directories on the
**real workspace** (they have `Cloud = true`) and never reliably remove
them, so leftovers accumulate on shared test workspaces (e.g.
`azure-prod-ucws-is`), bloating `workspace list /`. This was observed
contributing to a workspace-listing integration test hanging.

Two distinct leaks:

1. **`genie_space`, `dashboard`, `alert`** each ran `workspace mkdirs
/Workspace/test-$UNIQUE_NAME` at the **workspace root** and used it as
the `parent_path` for the resource they create. Nothing deleted it: no
`script.cleanup`, and the `eng-dev-ecosystem` env cleaner only sweeps
`/Users`, never the root. The alert test also frequently times out
(`TimeoutCloud = "5m"`, #4221).
2. **`auto-bind`** deployed its bundle to `/Workspace/tmp/$UNIQUE_NAME`.
Its `bundle destroy` removes that on the happy path, but the inline
`trap` only cleaned the `/Users/.../python-*` notebook dirs — so a
failure before `destroy` leaked the root into the shared, unswept
`/Workspace/tmp` namespace.

## What

Every generate test that creates workspace state now cleans up after
itself, in the swept user tree:

- Relocated the three root dirs to
`/Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME`, and added a
`script.cleanup` to each that recursively deletes it (removing the genie
space / dashboard / alert created inside).
- Moved `auto-bind`'s bundle root to
`~/.bundle/auto-bind-test-$UNIQUE_NAME`, matching the `~/.bundle`
convention every other bundle acceptance test uses.

Output goldens regenerated with `-update`; the full `bundle/generate`
suite passes locally.

This pull request and its description were written by Isaac, an AI
coding agent.

Author: janniklasrose

acceptance/bundle/generate/alert/alert.json.tmpl

@@ -1,6 +1,6 @@
 {
   "display_name": "test alert",
-  "parent_path": "/Workspace/test-$UNIQUE_NAME",
+  "parent_path": "/Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME",
   "query_text": "SELECT 1\n as value",
   "warehouse_id": "$TEST_DEFAULT_WAREHOUSE_ID",
   "evaluation": {

acceptance/bundle/generate/alert/output.txt

@@ -1,5 +1,5 @@
 
->>> [CLI] workspace mkdirs /Workspace/test-[UNIQUE_NAME]
+>>> [CLI] workspace mkdirs /Workspace/Users/[USERNAME]/test-[UNIQUE_NAME]
 
 >>> [CLI] bundle generate alert --existing-id [ALERT_ID] --source-dir out/alert --config-dir out/resource
 Alert configuration successfully saved to [TEST_TMP_DIR]/out/resource/test_alert.alert.yml
@@ -12,3 +12,5 @@ so it will not be deployed. Add a matching entry to the 'include' section, for e
 include:
   - out/resource/*.yml
 
+
+>>> [CLI] workspace delete /Workspace/Users/[USERNAME]/test-[UNIQUE_NAME] --recursive

acceptance/bundle/generate/alert/script

@@ -1,4 +1,4 @@
-trace $CLI workspace mkdirs /Workspace/test-$UNIQUE_NAME
+trace $CLI workspace mkdirs /Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME
 
 # create an alert to import
 envsubst < alert.json.tmpl > alert.json

acceptance/bundle/generate/alert/script.cleanup

@@ -0,0 +1 @@
+trace $CLI workspace delete /Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME --recursive

acceptance/bundle/generate/auto-bind/databricks.yml.tmpl

@@ -2,7 +2,7 @@ bundle:
   name: auto-bind-test
 
 workspace:
-  root_path: /tmp/${UNIQUE_NAME}
+  root_path: ~/.bundle/auto-bind-test-${UNIQUE_NAME}
 
 include:
   - resources/*.yml

acceptance/bundle/generate/auto-bind/output.txt

@@ -21,7 +21,7 @@ test.py
 
 === Deploy the bound job:
 >>> [CLI] bundle deploy
-Uploading bundle files to /Workspace/tmp/[UNIQUE_NAME]/files...
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/auto-bind-test-[UNIQUE_NAME]/files...
 Deploying resources...
 Updating deployment state...
 Deployment complete!
@@ -31,7 +31,7 @@ Deployment complete!
 The following resources will be deleted:
   delete resources.jobs.test_job
 
-All files and directories at the following location will be deleted: /Workspace/tmp/[UNIQUE_NAME]
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/auto-bind-test-[UNIQUE_NAME]
 
 Deleting files...
 Destroy complete!

acceptance/bundle/generate/dashboard/dashboard.json.tmpl

@@ -1,5 +1,5 @@
 {
     "display_name": "test dashboard",
-    "parent_path": "/Workspace/test-$UNIQUE_NAME",
+    "parent_path": "/Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME",
     "serialized_dashboard": "{\"pages\":[{\"displayName\":\"New Page\",\"layout\":[],\"name\":\"12345678\"}]}"
 }

acceptance/bundle/generate/dashboard/output.txt

@@ -1,5 +1,5 @@
 
->>> [CLI] workspace mkdirs /Workspace/test-[UNIQUE_NAME]
+>>> [CLI] workspace mkdirs /Workspace/Users/[USERNAME]/test-[UNIQUE_NAME]
 
 >>> [CLI] bundle generate dashboard --existing-id [DASHBOARD_ID] --dashboard-dir out/dashboard --resource-dir out/resource
 Writing dashboard to out/dashboard/test_dashboard.lvdash.json
@@ -12,3 +12,5 @@ so it will not be deployed. Add a matching entry to the 'include' section, for e
 include:
   - out/resource/*.yml
 
+
+>>> [CLI] workspace delete /Workspace/Users/[USERNAME]/test-[UNIQUE_NAME] --recursive

acceptance/bundle/generate/dashboard/script

@@ -1,4 +1,4 @@
-trace $CLI workspace mkdirs /Workspace/test-$UNIQUE_NAME
+trace $CLI workspace mkdirs /Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME
 
 # create a dashboard to import
 envsubst < dashboard.json.tmpl > dashboard.json

acceptance/bundle/generate/dashboard/script.cleanup

@@ -0,0 +1 @@
+trace $CLI workspace delete /Workspace/Users/$CURRENT_USER_NAME/test-$UNIQUE_NAME --recursive