feat(aw): updating the workflow with latest aw

[ChronosSF]

Closes #

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in topic content has a valuable update, it's new or considered as preview\ beta
• link to other topics using ../relative/path.md
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check broken links (use browser add-on)
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)
• add pending-localization label when the review of the PR is done
• add a member from the localization team to translate it

[Copilot]

Pull request overview

Updates the gh-aw generated workflow used to sync Japanese docs with the latest gh-aw tooling versions and regenerated workflow structure.

Changes:

• Regenerates .github/workflows/sync-jp-docs.lock.yml for gh-aw v0.68.1 (new setup action, updated AWF/Copilot versions, revised job layout/artifacts).
• Adds new locked action entries in .github/aw/actions-lock.json for the updated gh-aw setup action and actions/github-script@v9.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/sync-jp-docs.lock.yml	Regenerated workflow to newer gh-aw version, updating actions, scripts paths, and job structure.
.github/aw/actions-lock.json	Updates the action lock manifest to include newer action versions/SHAs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

.github/aw/actions-lock.json pins actions/github-script@v9 to sha 373c709c..., but the workflow uses actions/github-script@3a2844b... in many places. This mismatch can break any validation that relies on actions-lock.json as the source of truth. Align the workflow to the pinned sha or update the lock to match the sha actually used (and keep it consistent across the workflow).

Suggested change

	"sha": "373c709c69115d41ff229c7e5df9f8788daa9553"
	"sha": "3a2844b..."

[Copilot]

The workflow uses two different pinned SHAs for actions/github-script v9 (3a2844b... here vs 373c709c... elsewhere). This makes the workflow harder to audit and also conflicts with .github/aw/actions-lock.json which only records one sha for v9. Prefer pinning all actions/github-script steps to a single sha that matches the lock file (or update the lock accordingly).

[Copilot]

This step pins actions/github-script to sha 373c709c... while the rest of the workflow largely pins 3a2844b.... Please standardize on a single sha for actions/github-script across the workflow (and ensure it matches .github/aw/actions-lock.json).