Test rearrangement fix - unrelated to catalog credentials

test_map_inside_composite_type runs first in the following suites
- test-check-pg-lake-table (17, check-pg_lake_table, 2)
- test-check-pg-lake-table (18, check-pg_lake_table, 2)
- test-installcheck-pg-lake-table (16, installcheck-pg_lake_table, 2)
before any test with the extension fixture has a chance to run.

The 2 at the end means these are shard 2 of a parallelized test run.
CI splits tests across multiple shards, and test_map_inside_composite_type
ended up in shard 2, while test_struct_map_child_lookup (which has the
extension fixture) ended up in shard 1. This change comes from the fact
that this PR introduces a lot of new tests, which likely changed the
distribution.

Fix: add extension to test_map_inside_composite_type

Signed-off-by: sfc-gh-npuka <naisila.puka@snowflake.com>

Author: sfc-gh-npuka

pg_lake_table/tests/pytests/test_complex_types.py

@@ -194,7 +194,7 @@ def test_struct_from_user_composite_type(pg_conn, extension):
 
 
 # This test verifies #788 behavior and fix for a MAP type as part of a composite type
-def test_map_inside_composite_type(pg_conn):
+def test_map_inside_composite_type(pg_conn, extension):
     url = f"s3://{TEST_BUCKET}/test_map_inside_composite_type/data.parquet"
 
     map_type_name = create_map_type("int", "text")