Figma sync tokens update scope on sync

What does this MR do?

Figma sync tokens update scope on sync

Related to: #3508 (closed)

Validation instructions

Get Figma token

To get your Figma API token (FIGMA_DESIGN_TOKEN_SYNC_ACCESS_TOKEN):

1. In Figma homepage, click profile picture and select "Settings"
2. Go to "Security" tab
3. In "Personal access tokens" section press "Generate new token"
4. Give your token a descriptive name and select scopes: 4.1 file_content:read 4.2 file_variables:read 4.3 file_variables:write
5. Copy the generated token (starts with "figd_")

Get Figma File ID

To get the Figma file ID (FIGMA_DESIGN_TOKEN_FILE_ID): This should point to the design token library file

1. Open the [design token library Figma file](https://www.figma.com/design/tiAetVi1j5MGP8WA5FswcD/Design-tokens?node-id=0-1&p=f&t=NSh8oe7blzt9OVQe-
2. Create a branch in Figma
3. Copy the BRANCH_ID from URL: https://www.figma.com/design/{FILE_ID}/branch/{BRANCH_ID}

Add both to .figma.env as:

1. FIGMA_DESIGN_TOKEN_SYNC_ACCESS_TOKEN
2. FIGMA_DESIGN_TOKEN_FILE_ID

Run yarn sync-tokens in /packages/gitlab-ui

Should get output like:

$ node --env-file=.figma.env bin/figma_sync_tokens.mjs
Fetching existing variables...
Found 1018 variables in 2 collections

=== Syncing Constants ===
Fetching existing variables...
Found 1018 variables in 2 collections

=== Syncing Mode ===
Updating scopes for 136 variables...
  Batch 1/2...
  Batch 2/2...

═══════════════════════════════════════
✓ Token sync completed successfully
═══════════════════════════════════════
Constants: 0 created, 0 updated
Mode:      0 created, 136 updated
Total:     0 created, 136 updated
═══════════════════════════════════════
✨  Done in 9.42s.

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

• The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
  • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
• Relevant label(s) are applied to the MR.
• The MR is added to a milestone.
• Added the ~"component:*" label(s) if applicable.
• A changeset is added when this MR will do a patch, minor, or major update. More information can be found in doc/changesets.md.

Components

• GitLab UI's contributing guidelines.
• If the MR changes a component's API, integration MR(s) have been opened (see integrations above).

Documentation

• If creating a new component page from scratch, it follows the page template structure.
• Content follows the GitLab Documentation Style Guide when appropriate.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.
• Maintainer review follows the Pajamas UX maintainer review checklist.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

• All actions and functionality can be done with a keyboard.
• Links, buttons, and controls have a visible focus state.
• All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
• Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
• Color combinations have sufficient contrast.