acceptance/bundle/dms: add state-read test; refresh flag-on goldens

state-read builds a synthetic DMS deployment (deployment, version, and a job
resource) via raw API calls, points local state at it, and verifies `bundle
summary` resolves the job id from DMS ListResources rather than local state.

record/redeploy goldens are refreshed for the state-read wiring: until operation
recording lands, deploy records no resources in DMS, so a later read returns an
empty set (destroy/redeploy no longer see the prior job).

Author: shreyas-goenka

acceptance/bundle/dms/record/output.txt

@@ -55,9 +55,6 @@ Deployment complete!
 }
 
 >>> [CLI] bundle destroy --auto-approve
-The following resources will be deleted:
-  delete resources.jobs.foo
-
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/dms-record/default
 
 Deleting files...

acceptance/bundle/dms/redeploy/output.txt

@@ -66,9 +66,6 @@ Deployment complete!
 }
 
 >>> [CLI] bundle destroy --auto-approve
-The following resources will be deleted:
-  delete resources.jobs.foo
-
 All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/dms-redeploy/default
 
 Deleting files...

acceptance/bundle/dms/state-read/databricks.yml

@@ -0,0 +1,10 @@
+bundle:
+  name: dms-state-read
+
+experimental:
+  record_deployment_history: true
+
+resources:
+  jobs:
+    foo:
+      name: foo

acceptance/bundle/dms/state-read/out.test.toml

@@ -0,0 +1,48 @@
+
+=== Construct synthetic DMS state via raw API calls
+>>> [CLI] api post /api/2.0/bundle/deployments?deployment_id=synthetic-dep --json {"target_name":"default"}
+{
+  "name": "deployments/synthetic-dep",
+  "status": "DEPLOYMENT_STATUS_ACTIVE",
+  "target_name": "default"
+}
+
+>>> [CLI] api post /api/2.0/bundle/deployments/synthetic-dep/versions?version_id=1 --json {"cli_version":"test","version_type":"VERSION_TYPE_DEPLOY"}
+{
+  "cli_version": "test",
+  "name": "deployments/synthetic-dep/versions/1",
+  "status": "VERSION_STATUS_IN_PROGRESS",
+  "version_id": "1",
+  "version_type": "VERSION_TYPE_DEPLOY"
+}
+
+>>> [CLI] api post /api/2.0/bundle/deployments/synthetic-dep/versions/1/operations --json {"resource_key":"jobs.foo","resource_id":"9999","action_type":"OPERATION_ACTION_TYPE_CREATE","status":"OPERATION_STATUS_SUCCEEDED","state":{"name":"foo"}}
+{
+  "action_type": "OPERATION_ACTION_TYPE_CREATE",
+  "resource_id": "9999",
+  "resource_key": "jobs.foo",
+  "state": {
+    "name": "foo"
+  },
+  "status": "OPERATION_STATUS_SUCCEEDED"
+}
+
+=== Point local state at the synthetic deployment: lineage == deployment id, no local resource state
+=== bundle summary resolves jobs.foo id (9999) from DMS ListResources
+>>> [CLI] bundle summary
+Name: dms-state-read
+Target: default
+Workspace:
+  User: [USERNAME]
+  Path: /Workspace/Users/[USERNAME]/.bundle/dms-state-read/default
+Resources:
+  Jobs:
+    foo:
+      Name: foo
+      URL:  [DATABRICKS_URL]/jobs/9999?w=[NUMID]
+
+>>> print_requests.py --get //api/2.0/bundle/deployments/synthetic-dep/resources
+{
+  "method": "GET",
+  "path": "/api/2.0/bundle/deployments/synthetic-dep/resources"
+}

acceptance/bundle/dms/state-read/output.txt

@@ -0,0 +1,17 @@
+# Build a synthetic DMS deployment (id == state lineage) holding one job resource,
+# using raw API calls, then verify `bundle summary` reads that resource back from
+# DMS rather than from the local resources.json (which intentionally has no
+# resource state).
+
+title "Construct synthetic DMS state via raw API calls"
+trace $CLI api post '/api/2.0/bundle/deployments?deployment_id=synthetic-dep' --json '{"target_name":"default"}'
+trace $CLI api post '/api/2.0/bundle/deployments/synthetic-dep/versions?version_id=1' --json '{"cli_version":"test","version_type":"VERSION_TYPE_DEPLOY"}'
+trace $CLI api post '/api/2.0/bundle/deployments/synthetic-dep/versions/1/operations' --json '{"resource_key":"jobs.foo","resource_id":"9999","action_type":"OPERATION_ACTION_TYPE_CREATE","status":"OPERATION_STATUS_SUCCEEDED","state":{"name":"foo"}}'
+
+title "Point local state at the synthetic deployment: lineage == deployment id, no local resource state"
+mkdir -p .databricks/bundle/default
+printf '{"state_version":2,"lineage":"synthetic-dep","serial":1,"state":{}}\n' > .databricks/bundle/default/resources.json
+
+title "bundle summary resolves jobs.foo id (9999) from DMS ListResources"
+trace $CLI bundle summary
+trace print_requests.py --get //api/2.0/bundle/deployments/synthetic-dep/resources