Add telemetry for bundle init (#2537)

## Changes
This PR adds telemetry logging for the `databricks bundle init` command.

## Why
We would like to know how often our templates are used and what revenues
are associated with each of our templates.

## Tests
Acceptance tests. Here are the properties that we want to ensure:
1. For Databricks templates, only enum/bool args should be captured;
others should be ignored. Non-enum args are not safe for centralization.
2. For user-defined custom templates, we should not log either the
template name or any of it's arguments (including boolean / enums).
3. The serialized bundle-uuid in `databricks.yml` should be the same as
the one recorded in the telemetry payload.


Also manually verified that the information shows up in our telemetry
table.

Author: shreyas-goenka

acceptance/bundle/templates-machinery/test.toml

@@ -1 +1,10 @@
 Cloud = false
+
+[[Server]]
+Pattern = "POST /telemetry-ext"
+Response.Body = '''
+{
+    "errors": [],
+    "numProtoSuccess": 1
+}
+'''

acceptance/bundle/templates/telemetry/custom-template/databricks_template_schema.json

@@ -0,0 +1,17 @@
+{
+    "properties": {
+        "project_name": {
+            "type": "string",
+            "description": "The name of the project"
+        },
+        "some_enum": {
+            "type": "string",
+            "enum": [
+                "v1",
+                "v2",
+                "v3"
+            ],
+            "description": "An enum"
+        }
+    }
+}

acceptance/bundle/templates/telemetry/custom-template/input.json

@@ -0,0 +1,4 @@
+{
+    "project_name": "my_custom_template",
+    "some_enum": "v2"
+}

acceptance/bundle/templates/telemetry/custom-template/out.databricks.yml

@@ -0,0 +1,2 @@
+bundle:
+  uuid: [BUNDLE-UUID]

acceptance/bundle/templates/telemetry/custom-template/out.requests.txt

@@ -0,0 +1,16 @@
+{
+  "headers": {
+    "User-Agent": [
+      "cli/[DEV_VERSION] databricks-sdk-go/[SDK_VERSION] go/[GO_VERSION] os/[OS] cmd/bundle_init cmd-exec-id/[CMD-EXEC-ID] auth/pat"
+    ]
+  },
+  "method": "POST",
+  "path": "/telemetry-ext",
+  "body": {
+    "uploadTime": "UNIX_TIME_MILLIS",
+    "items": [],
+    "protoLogs": [
+      "{\"frontend_log_event_id\":\"[UUID]\",\"entry\":{\"databricks_cli_log\":{\"execution_context\":{\"cmd_exec_id\":\"[CMD-EXEC-ID]\",\"version\":\"[DEV_VERSION]\",\"command\":\"bundle_init\",\"operating_system\":\"[OS]\",\"execution_time_ms\":\"SMALL_INT\",\"exit_code\":0},\"bundle_init_event\":{\"bundle_uuid\":\"[BUNDLE-UUID]\",\"template_name\":\"custom\"}}}}"
+    ]
+  }
+}

acceptance/bundle/templates/telemetry/custom-template/output.txt

@@ -0,0 +1,3 @@
+
+>>> [CLI] bundle init . --config-file input.json --output-dir output
+✨ Successfully initialized template

acceptance/bundle/templates/telemetry/custom-template/script

@@ -0,0 +1,14 @@
+trace $CLI bundle init . --config-file input.json --output-dir output
+
+# We only need to keep the output databricks.yml to assert the bundle_uuid is consistent
+# in both the generated YAML file and telemetry payload.
+mv output/my_custom_template/databricks.yml out.databricks.yml
+rm -r output
+
+
+cmd_exec_id=$(cat out.requests.txt | jq '.headers."User-Agent".[0]'| head -n 1 | grep -o 'cmd-exec-id/[^ ]*' | cut -d '/' -f2)
+bundle_uuid=$(cat out.databricks.yml | grep -o 'uuid: [^\n]*' | cut -d ' ' -f2)
+
+update_file.py out.requests.txt $cmd_exec_id  '[CMD-EXEC-ID]'
+update_file.py out.requests.txt $bundle_uuid '[BUNDLE-UUID]'
+update_file.py out.databricks.yml $bundle_uuid '[BUNDLE-UUID]'

acceptance/bundle/templates/telemetry/custom-template/template/{{.project_name}}/databricks.yml.tmpl

@@ -0,0 +1,2 @@
+bundle:
+  uuid: {{bundle_uuid}}

acceptance/bundle/templates/telemetry/dbt-sql/input.json

@@ -0,0 +1,6 @@
+{
+    "project_name": "my_dbt_sql",
+    "http_path": "/sql/2.0/warehouses/f00dcafe",
+    "default_catalog": "main",
+    "personal_schemas": "yes, use a schema based on the current user name during development"
+}

acceptance/bundle/templates/telemetry/dbt-sql/out.databricks.yml

@@ -0,0 +1,32 @@
+# This file defines the structure of this project and how it is deployed
+# to production using Databricks Asset Bundles.
+# See https://docs.databricks.com/dev-tools/bundles/index.html for documentation.
+bundle:
+  name: my_dbt_sql
+  uuid: [BUNDLE-UUID]
+
+include:
+  - resources/*.yml
+
+# Deployment targets.
+# The default schema, catalog, etc. for dbt are defined in dbt_profiles/profiles.yml
+targets:
+  dev:
+    # The default target uses 'mode: development' to create a development copy.
+    # - Deployed resources get prefixed with '[dev my_user_name]'
+    # - Any job schedules and triggers are paused by default.
+    # See also https://docs.databricks.com/dev-tools/bundles/deployment-modes.html.
+    mode: development
+    default: true
+    workspace:
+      host: [DATABRICKS_URL]
+
+  prod:
+    mode: production
+    workspace:
+      host: [DATABRICKS_URL]
+      # We explicitly deploy to /Workspace/Users/[USERNAME] to make sure we only have a single copy.
+      root_path: /Workspace/Users/[USERNAME]/.bundle/${bundle.name}/${bundle.target}
+    permissions:
+      - user_name: [USERNAME]
+        level: CAN_MANAGE