Migrate gcs to new system tests design

[bhirsz]

Migrate GCS system tests/example dags to be compliant with new design (AIP-47).

Covers
airflow/providers/google/cloud/example_dags/example_gcs.py
airflow/providers/google/cloud/example_dags/example_gcs_timespan_file_transform.py
airflow/providers/google/cloud/example_dags/example_gcs_to_gcs.py
airflow/providers/google/cloud/example_dags/example_gcs_to_local.py
airflow/providers/google/cloud/example_dags/example_local_to_gcs.py
from #22447

[bhirsz]

The PR is bigger than I want but it's mostly because there are several setup fixtures in old design (in pytest classes) that can now be covered by operators - thus the structure changed and multiple examples had to be done in one go. Everything relates to gcs though.

[Bowrna]

@bhirsz
I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in this PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

[bhirsz]

I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in #22811 (comment) PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

I've commented in your PR. But I've also encountered this problem whenever I run the same DAG_ID twice in the same environment (resetting env or using unique name between runs helps). I will investigate why it happens.

[bhirsz]

I tried to write a similar system tests design for Elasticsearch and I was running into issues. (#22811)
Can you help me by telling me if you faced similar issues like the one in the comments in #22811 (comment) PR?
It would be helpful if you could check this PR and point out mistakes if there is any in it.

I've commented in your PR. But I've also encountered this problem whenever I run the same DAG_ID twice in the same environment (resetting env or using unique name between runs helps). I will investigate why it happens.

Resolved by changing State.NONE (which works only for Tasks) to State.Queued (default state for dag)

[potiuk]

Rebased it - to test it with the new CI based on Breeze mostly.

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[potiuk]

Stuff to fix :)

[bhirsz]

@potiuk All green :)