[CLEAN] Synthetic Benchmark PR #20177 - fix(prefect-gcp): prevent double-nesting in GcsBucket._resolve_path

[tomerqodo]

Benchmark PR PrefectHQ#20177

Type: Clean (correct implementation)

Original PR Title: fix(prefect-gcp): prevent double-nesting in GcsBucket._resolve_path
Original PR Description: closes PrefectHQ#20174

this pr fixes the GcsBucket._resolve_path double-nesting bug that occurs when storage_block_id is null (e.g., when context is serialized to remote workers like Ray).

changes

• add duplicate-prefix check in _resolve_path() to prevent double-nesting when path already starts with bucket_folder
• add regression test for the fix
• fix test_push_to_gcs fixture that had broken .prefectignore patterns due to leading whitespace
• add filterwarnings for upstream deprecation warnings (httplib2, pathspec, google.api_core, coolname)
• increase test harness timeout to 60s to fix CI flakiness on Python 3.11+ (see Unit tests randomly fail to connect to ephemeral Prefect API server PrefectHQ/prefect#16397)

prior art

this is the same fix that was applied to _join_bucket_folder in PrefectHQ#18237 - the _resolve_path method had the same bug but wasn't fixed at that time.

reproduction script

from prefect_gcp.cloud_storage import GcsBucket

bucket = GcsBucket(bucket="test-bucket", bucket_folder="results/")

# simulate what happens when storage_block_id is null:
# create_result_record() adds bucket_folder to storage_key
already_prefixed_path = "results/abc123"

# before fix: returns "results/results/abc123" (double-nested)
# after fix: returns "results/abc123" (correct)
result = bucket._resolve_path(already_prefixed_path)
print(f"Result: {result}")
assert not result.startswith("results/results/"), f"Double nesting detected: {result}"

🤖 Generated with Claude Code
Original PR URL: PrefectHQ#20177