Hide --bind flag for generate command (#3840)

## Changes
Hide --bind flag for generate command

## Tests
Exisiting acceptance tests

Author: andrewnester

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

@@ -36,7 +36,6 @@ Usage:
   databricks bundle generate dashboard [flags]
 
 Flags:
-  -b, --bind                   automatically bind the generated dashboard config to the existing dashboard
   -s, --dashboard-dir string   directory to write the dashboard representation to (default "src")
       --existing-id string     ID of the dashboard to generate configuration for
       --existing-path string   workspace path of the dashboard to generate configuration for

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

@@ -28,7 +28,6 @@ Usage:
   databricks bundle generate job [flags]
 
 Flags:
-  -b, --bind                  automatically bind the generated resource to the existing resource
   -d, --config-dir string     Dir path where the output config will be stored (default "resources")
       --existing-job-id int   Job ID of the job to generate config for
   -f, --force                 Force overwrite existing files in the output directory

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

@@ -28,7 +28,6 @@ Usage:
   databricks bundle generate pipeline [flags]
 
 Flags:
-  -b, --bind                          automatically bind the generated resource to the existing resource
   -d, --config-dir string             Dir path where the output config will be stored (default "resources")
       --existing-pipeline-id string   ID of the pipeline to generate config for
   -f, --force                         Force overwrite existing files in the output directory

cmd/bundle/generate/app.go

@@ -59,6 +59,7 @@ per target environment.`,
 	cmd.Flags().StringVarP(&sourceDir, "source-dir", "s", "src/app", `Directory path where the app files will be stored`)
 	cmd.Flags().BoolVarP(&force, "force", "f", false, `Force overwrite existing files in the output directory`)
 	cmd.Flags().BoolVarP(&bind, "bind", "b", false, `automatically bind the generated app config to the existing app`)
+	cmd.Flags().MarkHidden("bind")
 
 	cmd.RunE = func(cmd *cobra.Command, args []string) error {
 		ctx := logdiag.InitContext(cmd.Context())

cmd/bundle/generate/dashboard.go

@@ -504,6 +504,7 @@ bundle files automatically, useful during active dashboard development.`,
 	cmd.Flags().BoolVarP(&d.force, "force", "f", false, `force overwrite existing files in the output directory`)
 
 	cmd.Flags().BoolVarP(&d.bind, "bind", "b", false, `automatically bind the generated dashboard config to the existing dashboard`)
+	cmd.Flags().MarkHidden("bind")
 
 	// Exactly one of the lookup flags must be provided.
 	cmd.MarkFlagsOneRequired(

cmd/bundle/generate/job.go

@@ -63,6 +63,7 @@ After generation, you can deploy this job to other targets using:
 	cmd.Flags().StringVarP(&sourceDir, "source-dir", "s", "src", `Dir path where the downloaded files will be stored`)
 	cmd.Flags().BoolVarP(&force, "force", "f", false, `Force overwrite existing files in the output directory`)
 	cmd.Flags().BoolVarP(&bind, "bind", "b", false, `automatically bind the generated resource to the existing resource`)
+	cmd.Flags().MarkHidden("bind")
 
 	cmd.RunE = func(cmd *cobra.Command, args []string) error {
 		ctx := logdiag.InitContext(cmd.Context())

cmd/bundle/generate/pipeline.go

@@ -62,6 +62,7 @@ like catalogs, schemas, and compute configurations per target.`,
 	cmd.Flags().StringVarP(&sourceDir, "source-dir", "s", "src", `Dir path where the downloaded files will be stored`)
 	cmd.Flags().BoolVarP(&force, "force", "f", false, `Force overwrite existing files in the output directory`)
 	cmd.Flags().BoolVarP(&bind, "bind", "b", false, `automatically bind the generated resource to the existing resource`)
+	cmd.Flags().MarkHidden("bind")
 
 	cmd.RunE = func(cmd *cobra.Command, args []string) error {
 		ctx := logdiag.InitContext(cmd.Context())