feat: New apps commands (#4247)

## Changes

### Overview
This PR adds new AppKit development commands to `databricks apps`,
making them first-class citizens alongside the auto-generated Apps API
commands. The implementation follows the same pattern established by the
`pipelines` commands.

### New Command Structure

`databricks apps` now has three command groups:

| Group | Commands | Description |
|-------|----------|-------------|
| **Available Commands** | `deploy`, `dev-remote`, `init`, `logs`,
`run-local`, `validate` | Custom development commands |
| **Management Commands** | `create`, `delete`, `get`, `list`, `start`,
`stop`, etc. | Auto-generated API commands |
| **Permission Commands** | `get-permissions`, `set-permissions`, etc. |
Permission management |


### Key Features

1. `databricks apps init` - Initialize new AppKit projects from
templates with interactive prompts, but also allowing full prompt
override via flags.
2. `databricks apps dev-remote` - Run local Vite dev server with
WebSocket bridge to remote app (this command already exists, but now has
some improvements like deriving the project from the folder and
reconnecting).
3. `databricks apps validate` - Run validation of the app running type
checking, linting and building.
4. `databricks apps deploy` - Dual-mode deployment:
- Bundle mode (when databricks.yml exists): Validates → Deploys bundle →
Runs app
    - API mode: Standard API deployment with APP_NAME argument


### Directory Structure
```
cmd/apps/                    # Custom commands
├── apps.go                  # Commands() + ManagementGroupID
├── init.go                  # Initialize projects
├── dev.go                   # Dev-remote command
├── deploy_bundle.go         # Bundle-aware deploy
├── logs.go                  # App logs
├── run_local.go               # Run locally
└── validate.go             # Validate the project compiles

cmd/workspace/apps/          # Auto-generated + overrides
├── apps.go                  # SDK commands
├── overrides.go             # Imports cmd/apps, groups commands
└── errors.go                # Error handling

libs/apps/                   # Shared libraries
├── features/                # Feature definitions
├── prompt/                  # Interactive prompts
├── validation/              # Project validation
└── vite/                    # Vite bridge
```


## 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? -->

## Tests
<!-- How have you tested the changes? -->

<!-- If your PR needs to be included in the release notes for next
release,
add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->

---------

Co-authored-by: MarioCadenas <MarioCadenas@users.noreply.github.com>

Author: MarioCadenas

NOTICE

@@ -82,6 +82,10 @@ charmbracelet/bubbletea - https://github.com/charmbracelet/bubbletea
 Copyright (c) 2020-2025 Charmbracelet, Inc
 License - https://github.com/charmbracelet/bubbletea/blob/master/LICENSE
 
+charmbracelet/huh - https://github.com/charmbracelet/huh
+Copyright (c) 2023 Charmbracelet, Inc.
+License - https://github.com/charmbracelet/huh/blob/main/LICENSE
+
 charmbracelet/lipgloss - https://github.com/charmbracelet/lipgloss
 Copyright (c) 2021-2025 Charmbracelet, Inc
 License - https://github.com/charmbracelet/lipgloss/blob/master/LICENSE

acceptance/apps/deploy/bundle-no-args/app/app.py

@@ -0,0 +1,2 @@
+# Minimal app for testing
+print("Hello from app")

acceptance/apps/deploy/bundle-no-args/databricks.yml

@@ -0,0 +1,8 @@
+bundle:
+  name: test-bundle
+
+resources:
+  apps:
+    myapp:
+      name: myapp
+      source_code_path: ./app

acceptance/apps/deploy/bundle-no-args/out.test.toml

@@ -0,0 +1,22 @@
+
+>>> [CLI] apps deploy --skip-validation
+Deploying bundle...
+Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/default/files...
+Deploying resources...
+Updating deployment state...
+Deployment complete!
+✓ Getting the status of the app myapp
+✓ App is in RUNNING state
+✓ App compute is in ACTIVE state
+✓ Deployment succeeded
+You can access the app at myapp-123.cloud.databricksapps.com
+✔ Deployment complete!
+
+>>> [CLI] bundle destroy --auto-approve
+The following resources will be deleted:
+  delete resources.apps.myapp
+
+All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/test-bundle/default
+
+Deleting files...
+Destroy complete!

acceptance/apps/deploy/bundle-no-args/output.txt

@@ -0,0 +1,7 @@
+# Test: apps deploy in a bundle directory without APP_NAME
+# Expected: Bundle deploy flow with validation + deploy + run app
+# Using --skip-validation since we're testing the deploy flow, not validation
+
+trace $CLI apps deploy --skip-validation
+
+trace $CLI bundle destroy --auto-approve

acceptance/apps/deploy/bundle-no-args/script

@@ -0,0 +1,37 @@
+Local = true
+Cloud = false
+
+Ignore = [
+    '.databricks',
+]
+
+[EnvMatrix]
+  DATABRICKS_BUNDLE_ENGINE = ["terraform", "direct"]
+
+[[Server]]
+Pattern = "POST /api/2.0/apps/myapp/deployments"
+Response.Body = '''
+{
+  "deployment_id": "dep-123",
+  "source_code_path": "/Workspace/apps/myapp",
+  "mode": "SNAPSHOT",
+  "status": {
+    "state": "SUCCEEDED",
+    "message": "Deployment succeeded"
+  }
+}
+'''
+
+[[Server]]
+Pattern = "GET /api/2.0/apps/myapp/deployments/dep-123"
+Response.Body = '''
+{
+  "deployment_id": "dep-123",
+  "source_code_path": "/Workspace/apps/myapp",
+  "mode": "SNAPSHOT",
+  "status": {
+    "state": "SUCCEEDED",
+    "message": "Deployment succeeded"
+  }
+}
+'''

acceptance/apps/deploy/bundle-no-args/test.toml

@@ -0,0 +1,8 @@
+bundle:
+  name: test-bundle
+
+resources:
+  apps:
+    myapp:
+      name: myapp
+      source_code_path: .

acceptance/apps/deploy/bundle-with-appname/databricks.yml

@@ -0,0 +1,5 @@
+{
+  "method": "POST",
+  "path": "/api/2.0/apps/test-app/deployments",
+  "body": {}
+}