Fix and complete the Japanese Circular Progress topics (xplat + Angular)

[jsakamotoIGJP]

Reworks the Japanese Circular Progress topics against their English sources. Both JP pages had sections left in English, and the xplat page also had broken MDX structure.

What changed

docs/xplat/src/content/jp/components/inputs/circular-progress.mdx

• Fixed broken MDX structure. The Progress Types Blazor PlatformBlock was never closed and its code fence was indented, and the Indeterminate Progress section was cut off mid-way with the English source duplicated after it. PlatformBlock tags (37) and code fences (44) now match the English topic exactly.
• Translated everything from Indeterminate Progress onward, which was still English: Animation Duration, Gradient Progress, the DocsAside note, Styling, the CSS parts table, API References, and Additional Resources.
• Picked up two English source updates the JP page had missed: the rewritten Gradient Progress paragraph, and the ApiLink for labelFormat.

docs/angular/src/content/jp/components/circular-progress.mdx

• Translated the intro <div class="highlight"> paragraph, which was still English.
• Added the second DocsAside about the default step / max increment, which was missing from the JP page.
• Reviewed the existing translation and fixed awkward wording, and unified the term for the circular progress bar, which appeared in three different spacings.
• Corrected the Styling intro, which still described a component mixin instead of the tokens() mixin the English topic now mentions.

Terminology

Wording and spacing follow the existing JP linear-progress topics in both doc sets, so terms like "アニメーション期間", "スタイル設定", "CSS パーツ", and "その他のリソース" stay consistent across the site.

Anchors

The JP heading rename does not break any anchors. Nothing links to these pages' heading anchors from other topics or from toc.json, and the in-page [スタイル設定セクション](#スタイル設定) link in the Angular topic resolves against the JP heading, matching how other JP topics build anchors.

Checks run

• npm run check:llms-metadata passed
• npx cspell on both changed files reported 0 issues
• npm run check-mdx-links:broken:angular reported no broken links in the changed files

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
• link to other topics using ./page.mdx or ../relative/path.mdx (.mdx extension required)
• 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 if links function by running the check-api/mdx npm commands
• 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
• add or update meaningful llms.description metadata and run npm run check:llms-metadata

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

• do not resolve requested changes (leave that to the reviewer)

🤖 Generated with Claude Code