Enable test_spog_workspace_google_credentials (databricks#1450)

## 🥞 Stacked PR
Use this
[link](https://github.com/databricks/databricks-sdk-py/pull/1450/files)
to review incremental changes.
-
[**stack/hectorcastejon/enable-spog-workspace-google-credentials**](databricks#1450)
[[Files
changed](https://github.com/databricks/databricks-sdk-py/pull/1450/files)]

---------
<!--
  This template provides a recommended structure for PR descriptions.
  Adapt it freely — the goal is clarity, not rigid compliance.
The three-section format (Summary / Why / What Changed) helps reviewers
understand the change quickly and makes the PR easier to revisit later.
-->

## Summary

Enable test after server side issues have been fixed.

## How is this tested?
N/A

NO_CHANGELOG=true

Author: hectorcast-db

tests/integration/test_unified_profile.py

@@ -87,12 +87,6 @@ def test_spog_workspace_azure_client_secret(isolated_env):
 
 # Environment: gcp-prod-ucacct
 def test_spog_workspace_google_credentials(isolated_env):
-    # google-credentials uses a GCP ID token with target_audience=cfg.host.
-    # On the unified host this produces the same token for both account and workspace
-    # requests (identical OIDC exchange, identical audience). Account-level APIs accept
-    # this token, but workspace-level APIs return 401. The X-Databricks-Org-Id header
-    # is set correctly. This appears to be a server-side limitation on unified hosts.
-    pytest.skip("google-credentials ID token is rejected for workspace operations on unified hosts")
     env = isolated_env("ucacct")
     host = env("UNIFIED_HOST")
     account_id = env("DATABRICKS_ACCOUNT_ID")