doc(Localization): update locale json files

[ArgoZhang]

Link issues

fixes #7724

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Update localization JSON resources and project references to them.

Enhancements:

• Align the project file and solution with the updated set of localization JSON resources.

Documentation:

• Refresh and correct locale JSON files for multiple languages, including adjusting file paths where needed.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• For the newly added/relocated localization/km-KH.json, double-check that the culture name and file path are consistent with how other locale files are referenced in BootstrapBlazor.csproj and consumed at runtime (e.g., same folder, naming pattern, and build action).
• In BootstrapBlazor.csproj and the solution file, keep the locale JSON entries grouped and alphabetically ordered like the existing ones to make future maintenance and additions easier.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- For the newly added/relocated `localization/km-KH.json`, double-check that the culture name and file path are consistent with how other locale files are referenced in `BootstrapBlazor.csproj` and consumed at runtime (e.g., same folder, naming pattern, and build action).
- In `BootstrapBlazor.csproj` and the solution file, keep the locale JSON entries grouped and alphabetically ordered like the existing ones to make future maintenance and additions easier.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This pull request updates localization files for the EditDialog component and releases version 10.3.3 of BootstrapBlazor. The changes add close confirmation dialog strings (CloseConfirmTitle and CloseConfirmContent) to all supported locale files in the /localization directory, bringing them in sync with the reference locale files in src/BootstrapBlazor/Locales/.

Changes:

• Updated version from 10.3.3-beta02 to 10.3.3 (release version)
• Added CloseConfirmTitle and CloseConfirmContent keys to 10 locale files (de, es, it, km-KH, pt-BR, pt, ru-RU, th-TH, uk-UA, zh-TW)
• Added km-KH.json to the solution file in alphabetical order

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/BootstrapBlazor/BootstrapBlazor.csproj	Version bump from 10.3.3-beta02 to 10.3.3 release
localization/zh-TW.json	Added close confirmation dialog strings in Traditional Chinese
localization/uk-UA.json	Added close confirmation dialog strings in Ukrainian
localization/th-TH.json	Added close confirmation dialog strings in Thai
localization/ru-RU.json	Added close confirmation dialog strings in Russian
localization/pt.json	Added close confirmation dialog strings in Portuguese
localization/pt-BR.json	Added close confirmation dialog strings in Brazilian Portuguese
localization/km-KH.json	Added close confirmation dialog strings in Khmer
localization/it.json	Added close confirmation dialog strings in Italian
localization/es.json	Added close confirmation dialog strings in Spanish
localization/de.json	Added close confirmation dialog strings in German
BootstrapBlazor.slnx	Added km-KH.json to solution file in correct alphabetical order

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (662be40) to head (6d30b78).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #7725   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          750       750           
  Lines        33268     33269    +1     
  Branches      4612      4612           
=========================================
+ Hits         33268     33269    +1     

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.