fix(GitHub Actions): Workflows fail on forked branches

[Aaron-Detre]

Changes

• generate-messages.yml now checks whether the pull request is from a fork or from the main project.
• If the PR is on the main project, it acts the same as before:
  • If there are no i18n changes required, the workflow succeeds.
  • If there are i18n changes required, it runs extract-i18n and commits the changes.
• If the PR is on a fork:
  • If there are no i18n changes required, the workflow succeeds.
  • If there are i18n changes required, the workflow fails with a message telling the author to run extract-i18n locally and commit the changes.
• I also fixed various errors that were present in generate-messages.yml and other-branch-workflows.yml

Test

• Testing GitHub Actions Changes From Fork
  • "test commit 2 (no i18n changes)" (which turned out to require i18n changes because I never undid the change from the original commit) failed with the error message.
  • "updated messages" succeeded because I ran extract-i18n locally and there were no more i18n changes required.
• Testing GitHub Actions Changes From Main Project
  • "test commit 2 (no i18n changes)" succeeded because there were no i18n changes required.
  • "test commit 3 (i18n changes required)" succeeded and automatically updated the messages.xlf

[qltysh]

Coverage Impact

Unable to calculate total coverage change because base branch coverage was not found.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.