Address Cursor review: clarify changelog and use .test TLD in fixture

- Changelog now notes that DATABRICKS_HOST still takes precedence over
  default_profile for `databricks auth token` (matches resolveNoArgsToken
  Step 1).
- Switch the auth token acceptance fixture from
  https://myworkspace.cloud.databricks.com to https://myworkspace.test
  per the repo's RFC 2606 convention; same for the secondary "other"
  profile in that file. Avoids reintroducing DNS/network flakiness.

Co-authored-by: Isaac

Author: janniklasrose

NEXT_CHANGELOG.md

@@ -6,7 +6,7 @@
 
 * `databricks auth describe` now reports where U2M (`databricks-cli`) tokens are stored: `plaintext` (`~/.databricks/token-cache.json`) or `secure` (OS keyring), and the source of the choice (env var, config setting, or default).
 * Marked the default profile in the interactive pickers shown by `databricks auth switch`, `databricks auth logout`, `databricks auth token`, and `databricks auth login`, and moved it to the top of the list. `databricks auth login` and `databricks auth logout` now offer the same selectors as `databricks auth token` and `databricks auth switch` respectively.
-* `[__settings__].default_profile` is now honored by `databricks api`, `databricks auth token`, and bundle commands when no `--profile` flag and no `DATABRICKS_CONFIG_PROFILE` env var is set. For bundle commands, `default_profile` only applies when the bundle does not pin its own `workspace.host`.
+* `[__settings__].default_profile` is now consulted as a fallback by `databricks api`, `databricks auth token`, and bundle commands when neither `--profile` nor `DATABRICKS_CONFIG_PROFILE` is set. `databricks auth token` continues to give precedence to `DATABRICKS_HOST` over `default_profile`. For bundle commands, `default_profile` only applies when the bundle does not pin its own `workspace.host`.
 
 ### Bundles
 

acceptance/cmd/auth/token/default-profile/output.txt

@@ -2,7 +2,7 @@
 === default_profile is honored when no args, --profile, or env var
 
 >>> errcode [CLI] auth token
-Warn: [hostmetadata] failed to fetch host metadata for https://myworkspace.cloud.databricks.com, will skip for 1m0s
+Warn: [hostmetadata] failed to fetch host metadata for https://myworkspace.test, will skip for 1m0s
 Error: cache: databricks OAuth is not configured for this host. Try logging in again with `databricks auth login --profile myprofile` before retrying. If this fails, please report this issue to the Databricks CLI maintainers at https://github.com/databricks/cli/issues/new
 
 Exit code: 1

acceptance/cmd/auth/token/default-profile/script

@@ -8,11 +8,11 @@ unset DATABRICKS_CONFIG_PROFILE
 # through to the non-interactive error "no profile specified".
 cat > "./home/.databrickscfg" <<'ENDCFG'
 [myprofile]
-host = https://myworkspace.cloud.databricks.com
+host = https://myworkspace.test
 auth_type = databricks-cli
 
 [other]
-host = https://other.example
+host = https://other.test
 auth_type = databricks-cli
 
 [__settings__]
@@ -25,7 +25,7 @@ trace errcode $CLI auth token
 title "default_profile pointing at a missing profile falls through to picker\n"
 cat > "./home/.databrickscfg" <<'ENDCFG'
 [myprofile]
-host = https://myworkspace.cloud.databricks.com
+host = https://myworkspace.test
 auth_type = databricks-cli
 
 [__settings__]