feat(healthcare): update the api

#### healthcare:v1beta1

The following keys were added:
- schemas.NotificationConfig.properties.sendForBulkImport.type (Total Keys: 1)

docs/dyn/healthcare_v1beta1.projects.locations.datasets.dicomStores.html

@@ -152,6 +152,7 @@ <h3>Method Details</h3>
   &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
   &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
     &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+    &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
   },
   &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
     { # StreamConfig specifies configuration for a streaming DICOM export.
@@ -180,6 +181,7 @@ <h3>Method Details</h3>
   &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
   &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
     &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+    &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
   },
   &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
     { # StreamConfig specifies configuration for a streaming DICOM export.
@@ -385,6 +387,7 @@ <h3>Method Details</h3>
   &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
   &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
     &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+    &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
   },
   &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
     { # StreamConfig specifies configuration for a streaming DICOM export.
@@ -516,6 +519,7 @@ <h3>Method Details</h3>
       &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
       &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
         &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+        &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
       },
       &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
         { # StreamConfig specifies configuration for a streaming DICOM export.
@@ -562,6 +566,7 @@ <h3>Method Details</h3>
   &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
   &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
     &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+    &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
   },
   &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
     { # StreamConfig specifies configuration for a streaming DICOM export.
@@ -590,6 +595,7 @@ <h3>Method Details</h3>
   &quot;name&quot;: &quot;A String&quot;, # Resource name of the DICOM store, of the form `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/dicomStores/{dicom_store_id}`.
   &quot;notificationConfig&quot;: { # Specifies where to send notifications upon changes to a data store. # Notification destination for new DICOM instances. Supplied by the client.
     &quot;pubsubTopic&quot;: &quot;A String&quot;, # The [Pub/Sub](https://cloud.google.com/pubsub/docs/) topic that notifications of changes are published on. Supplied by the client. PubsubMessage.Data contains the resource name. PubsubMessage.MessageId is the ID of this message. It is guaranteed to be unique within the topic. PubsubMessage.PublishTime is the time at which the message was published. Notifications are only sent if the topic is non-empty. [Topic names](https://cloud.google.com/pubsub/docs/overview#names) must be scoped to a project. Cloud Healthcare API service account must have publisher permissions on the given Pub/Sub topic. Not having adequate permissions causes the calls that send notifications to fail. If a notification can&#x27;t be published to Pub/Sub, errors are logged to Cloud Logging (see [Viewing error logs in Cloud Logging](https://cloud.google.com/healthcare/docs/how-tos/logging)). If the number of errors exceeds a certain rate, some aren&#x27;t submitted. Note that not all operations trigger notifications, see [Configuring Pub/Sub notifications](https://cloud.google.com/healthcare/docs/how-tos/pubsub) for specific details.
+    &quot;sendForBulkImport&quot;: True or False, # Indicates whether or not to send Pub/Sub notifications on bulk import. Only supported for DICOM imports.
   },
   &quot;streamConfigs&quot;: [ # A list of streaming configs used to configure the destination of streaming exports for every DICOM instance insertion in this DICOM store. After a new config is added to `stream_configs`, DICOM instance insertions are streamed to the new destination. When a config is removed from `stream_configs`, the server stops streaming to that destination. Each config must contain a unique destination.
     { # StreamConfig specifies configuration for a streaming DICOM export.