Convert TestLocalStateStaleness to an acceptance test (#3010)

## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->

A change in the series of changes for converting integration tests into
acceptance tests.
This will allow for easier testing of various backing solutions for
bundle deployment

Author: anton-107

acceptance/bundle/local_state_staleness/databricks.yml.tmpl

@@ -0,0 +1,18 @@
+bundle:
+  name: local-state-staleness-test
+
+workspace:
+  root_path: "~/.bundle/local-state-staleness-test-$UNIQUE_NAME"
+
+resources:
+  jobs:
+    test_job:
+      name: test-job-basic-$UNIQUE_NAME
+      tasks:
+        - task_key: my_notebook_task
+          new_cluster:
+            num_workers: 1
+            spark_version: $DEFAULT_SPARK_VERSION
+            node_type_id: $NODE_TYPE_ID
+          spark_python_task:
+            python_file: ./hello_world.py

acceptance/bundle/local_state_staleness/hello_world.py

@@ -0,0 +1 @@
+print("Hello world!")

acceptance/bundle/local_state_staleness/output.txt

@@ -0,0 +1,42 @@
+
+=== Step 1: Deploy bundle A
+>>> [CLI] bundle deploy --force-lock --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/local-state-staleness-test-[UNIQUE_NAME]/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Step 2: Deploy bundle B
+>>> [CLI] bundle deploy --force-lock --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/local-state-staleness-test-[UNIQUE_NAME]/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Step 3: Deploy bundle A again (should use remote state)
+>>> [CLI] bundle deploy --force-lock --auto-approve
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/local-state-staleness-test-[UNIQUE_NAME]/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+
+=== Step 4: Verify only one job exists
+{
+  "name": "test-job-basic-[UNIQUE_NAME]",
+  "id": [NUMID]
+}
+
+=== Cleanup - destroy bundle A (bundle B does not have an active deployment)
+
+>>> [CLI] bundle destroy --auto-approve
+The following resources will be deleted:
+  delete job test_job
+
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/local-state-staleness-test-[UNIQUE_NAME]
+
+Deleting files...
+Destroy complete!
+
+>>> rm -rf [TEST_TMP_DIR]/bundle_a
+
+>>> rm -rf [TEST_TMP_DIR]/bundle_b

acceptance/bundle/local_state_staleness/script

@@ -0,0 +1,44 @@
+# The approach for this test is as follows:
+# 1) First deploy of bundle instance A
+# 2) First deploy of bundle instance B
+# 3) Second deploy of bundle instance A
+# Because of deploy (2), the locally cached state of bundle instance A should be stale.
+# Then for deploy (3), it must use the remote state over the stale local state.
+
+envsubst < databricks.yml.tmpl > databricks.yml
+
+# Create two separate bundle directories to simulate two bundle instances
+BUNDLE_A_DIR="$TEST_TMP_DIR/bundle_a"
+BUNDLE_B_DIR="$TEST_TMP_DIR/bundle_b"
+
+mkdir -p "$BUNDLE_A_DIR" "$BUNDLE_B_DIR"
+
+# Copy bundle files to both directories
+cp databricks.yml hello_world.py "$BUNDLE_A_DIR/"
+cp databricks.yml hello_world.py "$BUNDLE_B_DIR/"
+
+cleanup() {
+    title "Cleanup - destroy bundle A (bundle B does not have an active deployment)\n"
+    cd "$BUNDLE_A_DIR" || exit
+    trace "$CLI" bundle destroy --auto-approve
+
+    trace rm -rf "$BUNDLE_A_DIR"
+    trace rm -rf "$BUNDLE_B_DIR"
+}
+trap cleanup EXIT
+
+title "Step 1: Deploy bundle A"
+cd "$BUNDLE_A_DIR"
+trace "$CLI" bundle deploy --force-lock --auto-approve
+
+title "Step 2: Deploy bundle B"
+cd "$BUNDLE_B_DIR"
+trace "$CLI" bundle deploy --force-lock --auto-approve
+
+title "Step 3: Deploy bundle A again (should use remote state)"
+cd "$BUNDLE_A_DIR"
+trace "$CLI" bundle deploy --force-lock --auto-approve
+
+title "Step 4: Verify only one job exists\n"
+cd "$BUNDLE_A_DIR"
+"$CLI" jobs list -o json | jq -r --arg name "test-job-basic-${UNIQUE_NAME}" '.[] | select(.settings.name == $name) | {name: .settings.name, id: .job_id}'

acceptance/bundle/local_state_staleness/test.toml

@@ -0,0 +1,2 @@
+Cloud = true
+Local = true