feat(v1): promote block_project_ssh_keys support to batch v1 API

PiperOrigin-RevId: 670424240

google/cloud/batch/v1/job.proto

@@ -442,6 +442,25 @@ message AllocationPolicy {
     // Optional. Set this field true if you want Batch to install Ops Agent on
     // your behalf. Default is false.
     bool install_ops_agent = 4 [(google.api.field_behavior) = OPTIONAL];
+
+    // Optional. Set this field to `true` if you want Batch to block
+    // project-level SSH keys from accessing this job's VMs.  Alternatively, you
+    // can configure the job to specify a VM instance template that blocks
+    // project-level SSH keys. In either case, Batch blocks project-level SSH
+    // keys while creating the VMs for this job.
+    //
+    // Batch allows project-level SSH keys for a job's VMs only if all
+    // the following are true:
+    //
+    // + This field is undefined or set to `false`.
+    // + The job's VM instance template (if any) doesn't block project-level
+    //   SSH keys.
+    //
+    // Notably, you can override this behavior by manually updating a VM to
+    // block or allow project-level SSH keys. For more information about
+    // blocking project-level SSH keys, see the Compute Engine documentation:
+    // https://cloud.google.com/compute/docs/connect/restrict-ssh-keys#block-keys
+    bool block_project_ssh_keys = 5 [(google.api.field_behavior) = OPTIONAL];
   }
 
   // A network interface.