Extract shared SelectProfile helper to eliminate duplicate profile pickers (#4647)

## 🥞 Stacked PR
Use this
[link](https://github.com/databricks/cli/pull/4647/files/e5a1d8842ee9a458d4ffb3cea672a0f88077356f..51f14b5c7ea409cffdc78a3025a70de5c674fa9a)
to review incremental changes.
- [stack/auth_logout](#4613)
[[Files changed](https://github.com/databricks/cli/pull/4613/files)]
-
[stack/auth_logout_profile_picker](#4616)
[[Files
changed](https://github.com/databricks/cli/pull/4616/files/c9e8d79e276d6c33faa1e859ca20cc5136f9efb7..e5a1d8842ee9a458d4ffb3cea672a0f88077356f)]
-
[**stack/auth_logout_deduplication**](#4647)
[[Files
changed](https://github.com/databricks/cli/pull/4647/files/e5a1d8842ee9a458d4ffb3cea672a0f88077356f..51f14b5c7ea409cffdc78a3025a70de5c674fa9a)]

---------
Four places built nearly identical `promptui.Select` prompts for
interactive profile selection (`auth logout`, `auth token`,
`cmd/root/auth.go`, `cmd/root/bundle.go`). This PR extracts a reusable
`profile.SelectProfile` function that accepts a declarative
`SelectConfig` with label, profiles, and template strings, replacing all
four implementations.

## Changes

- Add `profile.SelectProfile` in `libs/databrickscfg/profile/select.go`
— a shared interactive profile picker that accepts a `SelectConfig`
(label, profiles, template strings) and returns the selected profile
name.
- Replace the four inline `promptui.Select` implementations in
`cmd/auth/logout.go`, `cmd/auth/token.go`, `cmd/root/auth.go`, and
`cmd/root/bundle.go` with calls to `SelectProfile`.
- Add `AccountID` to `Profiles.SearchCaseInsensitive` so all pickers
support searching by account ID, not just name and host.
- Extract `writeConfigFile` helper in `libs/databrickscfg/ops.go` to
consolidate the repeated default-comment / backup / save sequence shared
by `SaveToProfile` and `DeleteProfile`.

## Why

The four profile pickers each duplicated the same prompt setup, searcher
wiring, and result extraction. This made it easy for behavior to diverge
(e.g., only the logout picker searched by account ID). A single shared
helper keeps the UX consistent and reduces the surface area for future
changes.

## Tests

- Existing unit and acceptance tests for `auth logout`, `auth token`,
workspace/account profile selection, and bundle profile resolution
continue to pass — the refactor is behavior-preserving.
- The `SelectProfile` helper is exercised indirectly through all
existing callers.

---------

Co-authored-by: simon <simon.faltum@databricks.com>

Author: mihaimitrea-db

acceptance/cmd/auth/logout/default-profile/out.databrickscfg

@@ -0,0 +1,7 @@
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+; Dev workspace
+[dev]
+host      = https://dev.cloud.databricks.com
+auth_type = databricks-cli

acceptance/cmd/auth/logout/default-profile/out.test.toml

@@ -0,0 +1,27 @@
+
+=== Initial config
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+host = https://default.cloud.databricks.com
+auth_type = databricks-cli
+
+; Dev workspace
+[dev]
+host = https://dev.cloud.databricks.com
+auth_type = databricks-cli
+
+=== Delete the DEFAULT profile
+>>> [CLI] auth logout --profile DEFAULT --force --delete
+Logged out of and deleted profile "DEFAULT".
+
+=== Backup file should exist
+OK: Backup file exists
+
+=== Config after logout — empty DEFAULT with comment should remain at the top of the file
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+; Dev workspace
+[dev]
+host      = https://dev.cloud.databricks.com
+auth_type = databricks-cli

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

@@ -0,0 +1,27 @@
+sethome "./home"
+
+cat > "./home/.databrickscfg" <<'EOF'
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+host = https://default.cloud.databricks.com
+auth_type = databricks-cli
+
+; Dev workspace
+[dev]
+host = https://dev.cloud.databricks.com
+auth_type = databricks-cli
+EOF
+
+title "Initial config\n"
+cat "./home/.databrickscfg"
+
+title "Delete the DEFAULT profile"
+trace $CLI auth logout --profile DEFAULT --force --delete
+
+title "Backup file should exist\n"
+assert_backup_exists
+
+title "Config after logout — empty DEFAULT with comment should remain at the top of the file\n"
+cat "./home/.databrickscfg"
+
+cp "./home/.databrickscfg" "./out.databrickscfg"

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

@@ -0,0 +1,31 @@
+
+=== Initial config
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+[dev]
+host = https://dev.cloud.databricks.com
+token = dev-pat-token
+
+=== Logout without --delete — should report no changes for non-U2M profile
+>>> [CLI] auth logout --profile dev --force
+No tokens to clear for profile "dev". Use --delete to remove it from the config file.
+
+=== Config after logout — profile should be unchanged
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+[dev]
+host = https://dev.cloud.databricks.com
+token = dev-pat-token
+
+=== Logout with --delete — should delete the profile
+>>> [CLI] auth logout --profile dev --force --delete
+Deleted profile "dev" with no tokens to clear.
+
+=== Backup file should exist
+OK: Backup file exists
+
+=== Config after delete — profile should be removed
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]

acceptance/cmd/auth/logout/delete-pat-token-profile/out.test.toml

@@ -0,0 +1,28 @@
+sethome "./home"
+
+cat > "./home/.databrickscfg" <<'EOF'
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+[dev]
+host = https://dev.cloud.databricks.com
+token = dev-pat-token
+EOF
+
+title "Initial config\n"
+cat "./home/.databrickscfg"
+
+title "Logout without --delete — should report no changes for non-U2M profile"
+trace $CLI auth logout --profile dev --force
+
+title "Config after logout — profile should be unchanged\n"
+cat "./home/.databrickscfg"
+
+title "Logout with --delete — should delete the profile"
+trace $CLI auth logout --profile dev --force --delete
+
+title "Backup file should exist\n"
+assert_backup_exists
+
+title "Config after delete — profile should be removed\n"
+cat "./home/.databrickscfg"

acceptance/cmd/auth/logout/delete-pat-token-profile/output.txt

@@ -0,0 +1,10 @@
+
+=== Logout of non-existent profile
+Error: profile "nonexistent" not found. Available profiles: dev
+
+Exit code: 1
+
+=== Logout without --profile in non-interactive mode
+Error: the command is being run in a non-interactive environment, please specify a profile to log out of using --profile
+
+Exit code: 1

acceptance/cmd/auth/logout/delete-pat-token-profile/script

@@ -0,0 +1,16 @@
+sethome "./home"
+
+cat > "./home/.databrickscfg" <<'EOF'
+; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
+[DEFAULT]
+
+[dev]
+host = https://dev.cloud.databricks.com
+auth_type = databricks-cli
+EOF
+
+title "Logout of non-existent profile\n"
+errcode $CLI auth logout --profile nonexistent --force
+
+title "Logout without --profile in non-interactive mode\n"
+errcode $CLI auth logout --force