remove multi_region_auxiliary from bq reservation

mmv1/products/bigqueryreservation/Reservation.yaml

@@ -65,12 +65,6 @@ properties:
     default_value: 0
     description: |
       Maximum number of queries that are allowed to run concurrently in this reservation. This is a soft limit due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency will be automatically set based on the reservation size.
-  - !ruby/object:Api::Type::Boolean
-    name: 'multiRegionAuxiliary'
-    description: |
-      Applicable only for reservations located within one of the BigQuery multi-regions (US or EU).
-      If set to true, this reservation is placed in the organization's secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization's default region.
-    deprecation_message: "`multi_region_auxiliary` is deprecated and will be removed in a future major release. This field is no longer supported by the BigQuery Reservation API."
   - !ruby/object:Api::Type::String
     name: 'edition'
     immutable: true

mmv1/third_party/terraform/website/docs/guides/version_6_upgrade.html.markdown

@@ -108,6 +108,12 @@ Description of the change and how users should adjust their configuration (if ne
 
 A `view` can no longer be created when `schema` contains required fields
 
+## Resource: `google_bigquery_reservation`
+
+### `multi_region_auxiliary` is now removed
+
+This field is no longer supported by the BigQuery Reservation API.
+
 ## Resource: `google_sql_database_instance`
 
 ### `settings.ip_configuration.require_ssl` is now removed