Prevent running certain workflows on forks

[AetherUnbound]

Fixes

Fixes #3693 by @AetherUnbound

Description

This PR prevents the following workflows from running on forks:

• generate_pot.yml
• issue_automations.yml
• label_sync.yml
• pr_automations.yml
• pr_automations_init.yml
• pr_ping.yml
• project_thread_update_reminders.yml
• release-app.yml
• renovate.yml
• subscribe_to_label.yml
• sync_meta.yml
• weekly_updates.yml

Testing Instructions

Merge and find out!

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

LGTM! While adding the if in some cases seems unnecessary (like release-app.yml which is dispatch-only), there is no drawback in having the check. Also great that it checks the owner instead of the repo name so the changes will work for the infra repo too when synced!

One small non-blocking request though, is that I think it would be nice to have some documentation on why these checks are present in the code.

[sarayourfriend]

LGTM! +1 to Dhruv's request for documentation, but non-blocking. It is kind of tedius to need to document it everywhere, and I don't know if documenting it in the CI/CD docs is discoverable... I wish it were easier (possible?) to template and DRY these yaml files 😮‍💨

[AetherUnbound]

Thanks for the quick review folks, and no worries! I can add comments in the same places 😄