Better inline documentation for bundle commands (#3353)

## Changes
I had cursor go through the bundle-examples repo and refer to those to
improve the docs we have for our bundle commands. Then edited them to be
correct.

## Why
Better docs.

Author: shreyas-goenka

acceptance/bundle/help/bundle-deploy/output.txt

@@ -1,6 +1,13 @@
 
 >>> [CLI] bundle deploy --help
-Deploy bundle
+Deploy bundle.
+
+Common patterns:
+  databricks bundle deploy                  # Deploy to default target (dev)
+  databricks bundle deploy --target dev     # Deploy to development
+  databricks bundle deploy --target prod    # Deploy to production
+
+See https://docs.databricks.com/en/dev-tools/bundles/index.html for more information.
 
 Usage:
   databricks bundle deploy [flags]

acceptance/bundle/help/bundle-deployment/output.txt

@@ -1,6 +1,20 @@
 
 >>> [CLI] bundle deployment --help
-Deployment related commands
+Deployment related commands for managing bundle resource bindings.
+
+Use these commands to bind / unbind bundle definitions to existing workspace resources.
+
+Common workflow:
+1. Generate configuration from existing resource:
+   databricks bundle generate job --existing-job-id 12345 --key my_job
+
+2. Bind the bundle resource to the existing workspace resource:
+   databricks bundle deployment bind my_job 12345
+
+3. Deploy updates - the bound resource will be updated in the workspace:
+   databricks bundle deploy
+
+After binding, the existing workspace resource will be managed by your bundle.
 
 Usage:
   databricks bundle deployment [command]

acceptance/bundle/help/bundle-destroy/output.txt

@@ -1,6 +1,17 @@
 
 >>> [CLI] bundle destroy --help
-Destroy deployed bundle resources
+Destroy all resources deployed by this bundle from the workspace.
+
+This command removes all Databricks resources that were created by deploying
+this bundle.
+
+Examples:
+  databricks bundle destroy                 # Destroy resources in default target
+  databricks bundle destroy --target prod   # Destroy resources in production target
+
+Typical use cases:
+- Cleaning up development or testing targets
+- Removing resources during environment decommissioning
 
 Usage:
   databricks bundle destroy [flags]

acceptance/bundle/help/bundle-generate-dashboard/output.txt

@@ -1,6 +1,36 @@
 
 >>> [CLI] bundle generate dashboard --help
-Generate configuration for a dashboard
+Generate bundle configuration for an existing Databricks dashboard.
+
+This command downloads an existing AI/BI dashboard and creates bundle files
+that you can use to deploy the dashboard to other environments or manage it as code.
+
+Examples:
+  # Import dashboard by workspace path
+  databricks bundle generate dashboard --existing-path /Users/me/sales-dashboard \
+    --key sales_dash
+
+  # Import dashboard by ID
+  databricks bundle generate dashboard --existing-id abc123 --key analytics_dashboard
+
+  # Watch for changes to keep bundle in sync with UI modifications
+  databricks bundle generate dashboard --resource my_dashboard --watch --force
+
+What gets generated:
+- Dashboard configuration YAML file with settings and a reference to the dashboard definition
+- Dashboard definition (.lvdash.json) file with layout and queries
+
+Sync workflow for dashboard development:
+When developing dashboards, you can modify them in the Databricks UI and sync
+changes back to your bundle:
+
+1. Make changes to dashboard in the Databricks UI
+2. Run: databricks bundle generate dashboard --resource my_dashboard --force
+3. Commit changes to version control
+4. Deploy to other environments with: databricks bundle deploy --target prod
+
+The --watch flag continuously polls for remote changes and updates your local
+bundle files automatically, useful during active dashboard development.
 
 Usage:
   databricks bundle generate dashboard [flags]

acceptance/bundle/help/bundle-generate-job/output.txt

@@ -1,6 +1,25 @@
 
 >>> [CLI] bundle generate job --help
-Generate bundle configuration for a job
+Generate bundle configuration for an existing Databricks job.
+
+This command downloads an existing job's configuration and creates bundle files
+that you can use to deploy the job to other environments or manage it as code.
+
+Examples:
+  # Import a production job for version control
+  databricks bundle generate job --existing-job-id 12345 --key my_etl_job
+
+  # Specify custom directories for organization
+  databricks bundle generate job --existing-job-id 67890 \
+    --key data_pipeline --config-dir resources --source-dir src
+
+What gets generated:
+- Job configuration YAML file in the resources directory
+- Any associated notebook or Python files in the source directory
+
+After generation, you can deploy this job to other targets using:
+  databricks bundle deploy --target staging
+  databricks bundle deploy --target prod
 
 Usage:
   databricks bundle generate job [flags]

acceptance/bundle/help/bundle-generate-pipeline/output.txt

@@ -1,6 +1,25 @@
 
 >>> [CLI] bundle generate pipeline --help
-Generate bundle configuration for a pipeline
+Generate bundle configuration for an existing Delta Live Tables pipeline.
+
+This command downloads an existing DLT pipeline's configuration and any associated
+notebooks, creating bundle files that you can use to deploy the pipeline to other
+environments or manage it as code.
+
+Examples:
+  # Import a production DLT pipeline
+  databricks bundle generate pipeline --existing-pipeline-id abc123 --key etl_pipeline
+
+  # Organize files in custom directories
+  databricks bundle generate pipeline --existing-pipeline-id def456 \
+    --key data_transformation --config-dir resources --source-dir src
+
+What gets generated:
+- Pipeline configuration YAML file with settings and libraries
+- Pipeline notebooks downloaded to the source directory
+
+After generation, you can deploy to other environments and modify settings
+like catalogs, schemas, and compute configurations per target.
 
 Usage:
   databricks bundle generate pipeline [flags]

acceptance/bundle/help/bundle-generate/output.txt

@@ -1,6 +1,19 @@
 
 >>> [CLI] bundle generate --help
-Generate bundle configuration
+Generate bundle configuration from existing Databricks resources.
+
+Common patterns:
+  databricks bundle generate job --existing-job-id 123 --key my_job
+  databricks bundle generate dashboard --existing-path /my-dashboard --key sales_dash
+  databricks bundle generate dashboard --resource my_dashboard --watch --force  # Keep local copy in sync. Useful for development.
+  databricks bundle generate dashboard --resource my_dashboard --force # Do a one-time sync.
+
+Complete migration workflow:
+  1. Generate: databricks bundle generate job --existing-job-id 123 --key my_job
+  2. Bind: databricks bundle deployment bind my_job 123
+  3. Deploy: databricks bundle deploy
+
+Use --key to specify the resource name in your bundle configuration.
 
 Usage:
   databricks bundle generate [command]

acceptance/bundle/help/bundle-init/output.txt

@@ -1,6 +1,6 @@
 
 >>> [CLI] bundle init --help
-Initialize using a bundle template.
+Initialize using a bundle template to get started quickly.
 
 TEMPLATE_PATH optionally specifies which template to use. It can be one of the following:
 - default-python: The default Python template for Notebooks / Delta Live Tables / Workflows
@@ -11,6 +11,15 @@ TEMPLATE_PATH optionally specifies which template to use. It can be one of the f
 - a local file system path with a template directory
 - a Git repository URL, e.g. https://github.com/my/repository
 
+Examples:
+  databricks bundle init                   # Choose from built-in templates
+  databricks bundle init default-python    # Python jobs and notebooks
+  databricks bundle init dbt-sql           # dbt + SQL warehouse project
+  databricks bundle init --output-dir ./my-project
+
+After initialization:
+  databricks bundle deploy --target dev
+
 See https://docs.databricks.com/en/dev-tools/bundles/templates.html for more information on templates.
 
 Usage:

acceptance/bundle/help/bundle-open/output.txt

@@ -1,6 +1,13 @@
 
 >>> [CLI] bundle open --help
-Open a resource in the browser
+Open a deployed bundle resource in the Databricks workspace.
+
+Examples:
+  databricks bundle open                    # Prompts to select a resource to open
+  databricks bundle open my_job             # Open specific job in Workflows UI
+  databricks bundle open my_dashboard       # Open dashboard in browser
+
+Use after deployment to quickly navigate to your resources in the workspace.
 
 Usage:
   databricks bundle open [flags]

acceptance/bundle/help/bundle-schema/output.txt

@@ -1,6 +1,13 @@
 
 >>> [CLI] bundle schema --help
-Generate JSON Schema for bundle configuration
+Generate JSON Schema for bundle configuration to enable validation and autocomplete.
+
+This command outputs the JSON Schema that describes the structure and validation
+rules for Databricks Asset Bundle configuration files.
+
+Common use cases:
+- Configure IDE/editor validation for databricks.yml files
+- Set up autocomplete and IntelliSense for bundle configuration
 
 Usage:
   databricks bundle schema [flags]