Description

This PR fixes an issue where the Crowdin Action workflow was not triggering GitHub CI steps after making translation commits.

Problem:
The Crowdin Action workflow was configured with a token mismatch - the checkout step used the default GITHUB_TOKEN (with limited permissions), while the Crowdin action itself used METAMASKBOT_CROWDIN_TOKEN (PAT). This inconsistency prevented the workflow from having the necessary permissions to trigger subsequent CI workflows.

Solution:

• Removed the permissions section that was limiting the workflow to default token permissions
• Added the PAT (METAMASKBOT_CROWDIN_TOKEN) to the checkout step so both checkout and Crowdin action operations use the same token
• This ensures consistent authentication and proper permissions for triggering other workflows

The fix follows the same pattern used in the MetaMask Extension repository's Crowdin workflow.

Changelog

CHANGELOG entry: null

Related issues

Fixes: GitHub CI steps not triggering after Crowdin Action commits

Manual testing steps

1. Monitor the Crowdin Action workflow runs in the Actions tab
2. Verify that when the Crowdin Action makes translation commits, the CI workflow is triggered
3. Check that the bot commits are properly attributed to metamaskbot
4. Confirm that translation updates flow through the normal CI pipeline

Screenshots/Recordings

Before

• Crowdin Action would run but CI workflows would not be triggered by the resulting commits
• Token permission mismatch between checkout and action steps

After

• Crowdin Action commits should now properly trigger CI workflows
• Consistent token usage throughout the workflow

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.