[DOC-529] Add requirements for roles and scoping to GCP cloud logging for DBAL (yugabyte#24985)

* Add requirements for roles and scoping to GCP cloud logging for DBAL

* edits

---------

Co-authored-by: Dwight Hodge <ghodge@yugabyte.com>

Author: dataindataout

docs/content/preview/yugabyte-platform/alerts-monitoring/anywhere-export-configuration.md

@@ -113,7 +113,8 @@ To create an export configuration, do the following:
 
 The GCP Cloud Logging export configuration requires the following:
 
-- Google Service Account credentials JSON
+- Google Service Account with the `roles/logging.logWriter` role.
+- The Service Account credentials JSON key. The credentials should be scoped to the project where the log group is located.
 
 To create an export configuration, do the following:
 

docs/content/stable/yugabyte-platform/alerts-monitoring/anywhere-export-configuration.md

@@ -113,7 +113,8 @@ To create an export configuration, do the following:
 
 The GCP Cloud Logging export configuration requires the following:
 
-- Google Service Account credentials JSON
+- Google Service Account with the `roles/logging.logWriter` role.
+- The Service Account credentials JSON key. The credentials should be scoped to the project where the log group is located.
 
 To create an export configuration, do the following:
 

docs/content/v2024.2/yugabyte-platform/alerts-monitoring/anywhere-export-configuration.md

@@ -113,7 +113,8 @@ To create an export configuration, do the following:
 
 The GCP Cloud Logging export configuration requires the following:
 
-- Google Service Account credentials JSON
+- Google Service Account with the `roles/logging.logWriter` role.
+- The Service Account credentials JSON key. The credentials should be scoped to the project where the log group is located.
 
 To create an export configuration, do the following: