Fix: 403 Forbidden Google Storage Error in GBFS pipeline

[cka-y]

Describe the Bug

A total of 297 GBFS feeds are affected by a 403 Forbidden error when attempting to upload files to Google Cloud Storage.

Example Error:

Error processing GBFS files: 403 POST https://storage.googleapis.com/upload/storage/v1/b/mobilitydata-gbfs-snapshots-prod/o?uploadType=multipart: {
  "error": {
    "code": 403,
    "message": "functions-service-account@mobility-feeds-prod.iam.gserviceaccount.com does not have storage.objects.delete access to the Google Cloud Storage object.",
    "errors": [
      {
        "message": "functions-service-account@mobility-feeds-prod.iam.gserviceaccount.com does not have storage.objects.delete access to the Google Cloud Storage object.",
        "domain": "global",
        "reason": "forbidden"
      }
    ]
  }
}
: ('Request failed with status code', 403, 'Expected one of', <HTTPStatus.OK: 200>)

Affected Feeds (Sample Stable IDs):

['gbfs-nextbike_ng', 'gbfs-nextbike_tv', 'gbfs-bcycle_greenbikeslc', 'gbfs-nextbike_ea', 'gbfs-nextbike_xc', 'gbfs-bcycle_redding', 'gbfs-donkey_ge', ...]

---

Steps to Reproduce

1. Run the pipeline with any of the affected feeds listed above.
2. Observe the 403 Forbidden error when processing GBFS files.

---

Expected Results

The files should be processed successfully without encountering a 403 Forbidden error.

---

Actual Results

The pipeline fails due to a lack of necessary storage.objects.delete permissions for the service account:
functions-service-account@mobility-feeds-prod.iam.gserviceaccount.com.

---

Additional Notes

The issue appears to be related to insufficient permissions on the Google Cloud Storage bucket. The service account lacks the necessary storage.objects.delete access to manage objects in the bucket.

Recommendation: Investigate and update the service account permissions to include storage.objects.delete for the affected bucket.

---