Add note about GCS permission

[laur-p]

Pull Request/Issue Resolution

Description of Change:

I'm changing GCS docs to include optional permissions for the cleanup of incomplete files

Closes #ISSUE_NUMBER_HERE

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @timothy-kim and @KellieHawks as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @timothy-kim or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@timothy-kim	Data Infrastructure Platform Infrastructure Quality Infrastructure
@KellieHawks	Internal Tools Product Partnerships SDKs SMS
@bre-fitzgerald	Channels FIX Intelligence Reporting SMB
@lydia-xie	Email (Composition and Infrastructure) Ingestion Messaging

[vercel]

@laur-p is attempting to deploy a commit to the Braze Team on Vercel.

A member of the Team first needs to authorize it.