Fix --force-pull on bundle summary and bundle open (#5028)

## Why

`--force-pull` on `bundle summary` and `bundle open` is silently
ignored: both commands declare the flag but never pass it through, so
the local state cache is used even when the user explicitly asks for a
remote pull. Users see stale URLs or IDs and have no way to bypass the
cache short of deleting `.databricks/` by hand.

The flag works as expected on `pipelines open` and `bundle debug
states`.

## Changes

Wire `forcePull` into `ProcessOptions.AlwaysPull` in
`cmd/bundle/summary.go` and `cmd/bundle/open.go` so the flag reaches
`statemgmt.PullResourcesState`. This matches the pattern used in the two
commands where the flag already works.

No behavior change when the flag is unset.

## Test plan

- [x] New acceptance test `acceptance/bundle/state/force_pull_commands/`
asserts that a workspace-files state GET is issued only when
`--force-pull` is set, for both `bundle summary` and `bundle open`. Runs
under both engines via EnvMatrix.
- [x] Reverted the fix locally and confirmed the test fails with the
expected diff (missing state GETs), then restored.
- [x] \`make checks\` clean; state/help/open/summary/pipelines-open
acceptance suites all pass.

Author: simonfaltum

NEXT_CHANGELOG.md

@@ -6,4 +6,6 @@
 
 ### Bundles
 
+* Fixed `--force-pull` on `bundle summary` and `bundle open` so the flag bypasses the local state cache and reads state from the workspace.
+
 ### Dependency updates

acceptance/bundle/state/force_pull_commands/databricks.yml

@@ -0,0 +1,16 @@
+bundle:
+  name: force-pull-commands
+
+resources:
+  jobs:
+    foo:
+      name: foo
+      tasks:
+        - task_key: task
+          spark_python_task:
+            python_file: ./foo.py
+          environment_key: default
+      environments:
+        - environment_key: default
+          spec:
+            client: "2"

acceptance/bundle/state/force_pull_commands/foo.py

@@ -0,0 +1 @@
+print("hello")

acceptance/bundle/state/force_pull_commands/open

@@ -0,0 +1,2 @@
+#!/bin/bash
+echo "I AM BROWSER"

acceptance/bundle/state/force_pull_commands/out.test.toml

@@ -0,0 +1,35 @@
+
+>>> [CLI] bundle deploy
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/force-pull-commands/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Modify PATH so that real open is not run
+=== bundle summary without --force-pull: no remote state read
+
+>>> [CLI] bundle summary
+
+=== bundle summary --force-pull: remote state read
+
+>>> [CLI] bundle summary --force-pull
+{
+  "method": "GET",
+  "path": "/api/2.0/workspace-files/Workspace/Users/[USERNAME]/.bundle/force-pull-commands/default/state/STATE_FILENAME"
+}
+
+=== bundle open without --force-pull: no remote state read
+
+>>> [CLI] bundle open foo
+Opening browser at [DATABRICKS_URL]/jobs/[NUMID]?o=[NUMID]
+Error: exec: "open": cannot run executable found relative to current directory
+
+=== bundle open --force-pull: remote state read
+
+>>> [CLI] bundle open foo --force-pull
+Opening browser at [DATABRICKS_URL]/jobs/[NUMID]?o=[NUMID]
+Error: exec: "open": cannot run executable found relative to current directory
+{
+  "method": "GET",
+  "path": "/api/2.0/workspace-files/Workspace/Users/[USERNAME]/.bundle/force-pull-commands/default/state/STATE_FILENAME"
+}

acceptance/bundle/state/force_pull_commands/output.txt

@@ -0,0 +1,21 @@
+trace $CLI bundle deploy > /dev/null
+rm -f out.requests.txt
+
+title "Modify PATH so that real open is not run"
+export PATH=.:$PATH
+
+title "bundle summary without --force-pull: no remote state read\n"
+trace $CLI bundle summary > /dev/null
+print_requests.py --get //workspace-files/
+
+title "bundle summary --force-pull: remote state read\n"
+trace $CLI bundle summary --force-pull > /dev/null
+print_requests.py --get //workspace-files/
+
+title "bundle open without --force-pull: no remote state read\n"
+musterr trace $CLI bundle open foo > /dev/null
+print_requests.py --get //workspace-files/
+
+title "bundle open --force-pull: remote state read\n"
+musterr trace $CLI bundle open foo --force-pull > /dev/null
+print_requests.py --get //workspace-files/

acceptance/bundle/state/force_pull_commands/script

@@ -0,0 +1,17 @@
+Local = true
+Cloud = false
+RecordRequests = true
+
+# bundle open opens a browser; restrict to darwin to get stable output
+# (mirrors acceptance/bundle/open/test.toml).
+GOOS.windows = false
+GOOS.linux = false
+
+Ignore = [".databricks"]
+
+[EnvMatrix]
+  DATABRICKS_BUNDLE_ENGINE = ["terraform", "direct"]
+
+[[Repls]]
+Old = '(resources\.json|terraform\.tfstate)'
+New = 'STATE_FILENAME'

acceptance/bundle/state/force_pull_commands/test.toml

@@ -74,7 +74,8 @@ Use after deployment to quickly navigate to your resources in the workspace.`,
 				arg, err = resolveOpenArgument(ctx, b, args)
 				return err
 			},
-			InitIDs: true,
+			AlwaysPull: forcePull,
+			InitIDs:    true,
 		})
 		if err != nil {
 			return err

cmd/bundle/open.go

@@ -46,6 +46,7 @@ Useful after deployment to see what was created and where to find it.`,
 		} else {
 			b, err := utils.ProcessBundle(cmd, utils.ProcessOptions{
 				ReadState:        true,
+				AlwaysPull:       forcePull,
 				IncludeLocations: includeLocations,
 				InitIDs:          true,
 			})