Add note on preserving API response case style for kinds from non-asset APIs

docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/gcp/examples/mapping_extra_resources.md

@@ -148,3 +148,44 @@ Create an integration configuration for the resource. The integration configurat
               machineType: ".machineType"
         		# highlight-end
         ```
+
+
+
+### Case Style Preservation
+
+Certain APIs return properties in specific case styles (e.g., snake_case). By default, the GCP integration will convert these properties to camelCase. However, you can preserve the original API response case style for the following APIs:
+
+- Projects (`cloudresourcemanager.googleapis.com/Project`)
+- Organizations (`cloudresourcemanager.googleapis.com/Organization`)
+- Folders (`cloudresourcemanager.googleapis.com/Folder`)
+- Topics (`pubsub.googleapis.com/Topic`)
+- Subscriptions (`pubsub.googleapis.com/Subscription`)
+
+This feature is particularly useful for ensuring compatibility with downstream systems or processes that depend on the original case style from the API response.
+
+#### How to Enable Case Style Preservation
+
+To preserve the case style, set `preserveApiResponseCaseStyle: true` in the selector configuration for the relevant API. For example:
+
+```yaml
+- kind: pubsub.googleapis.com/Subscription
+    selector:
+      query: 'true'
+      preserveApiResponseCaseStyle: 'true'
+    port:
+      entity:
+        mappings:
+          identifier: .name
+
+ - kind: pubsub.googleapis.com/Topic
+    selector:
+      query: 'true'
+      preserveApiResponseCaseStyle: 'true'
+    port:
+      entity:
+        mappings:
+          identifier: .name
+          title: .name | split("/") | last
+```
+
+When `preserveApiResponseCaseStyle` is not set or set to `false` (default behavior), all property names will be converted to camelCase format regardless of their original case style in the API response.