docs: update Japanese row adding and editing topics

[mkamiishi]

Summary

Updated the Japanese Row Adding and Row Editing documentation to better align with the current English source.

Changes

• Updated the Japanese Row Adding topic.
• Updated the Japanese Row Editing topic.
• Removed outdated or duplicated text.
• Added missing translated descriptions from the English source.
• Preserved code snippets, component names, property names, event names, and API names.

Testing

• Compared the Japanese Row Adding topic with the English source.
• Compared the Japanese Row Editing topic with the English source.
• Verified the Japanese Web Components pages locally with npm run xplat:dev:web-components:jp.
• Confirmed that code snippets, component names, property names, event names, and API names are preserved.

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)