Merge pull request #96427 from openshift-cherrypick-robot/cherry-pick-95326-to-enterprise-4.19

[enterprise-4.19] mod docs OADP on GCP

Author: ShaunaDiaz

backup_and_restore/application_backup_and_restore/installing/installing-oadp-gcp.adoc

@@ -9,6 +9,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You install the OpenShift API for Data Protection (OADP) with Google Cloud Platform (GCP) by installing the OADP Operator. The Operator installs link:https://{velero-domain}/docs/v{velero-version}/[Velero {velero-version}].
 
 include::snippets/oadp-mtc-operator.adoc[]

modules/migration-configuring-gcp.adoc

@@ -8,6 +8,7 @@
 [id="migration-configuring-gcp_{context}"]
 = Configuring Google Cloud Platform
 
+[role="_abstract"]
 ifdef::installing-3-4,installing-mtc[]
 You configure a Google Cloud Platform (GCP) storage bucket as a replication repository for the {mtc-first}.
 endif::[]

modules/oadp-gcp-wif-cloud-authentication.adoc

@@ -6,6 +6,7 @@
 [id="oadp-gcp-wif-cloud-authentication_{context}"]
 = Google workload identity federation cloud authentication
 
+[role="_abstract"]
 Applications running outside Google Cloud use service account keys, such as usernames and passwords, to gain access to Google Cloud resources. These service account keys might become a security risk if they are not properly managed.
 
 With Google's workload identity federation, you can use Identity and Access Management (IAM) to offer IAM roles, including the ability to impersonate service accounts, to external identities. This eliminates the maintenance and security risks associated with service account keys.