Update message id to align with its use

[DaanHoogland]

Description

This PR fixes a label mismatch

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

[github-actions]

This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch.

[Copilot]

Pull Request Overview

This PR corrects a message ID mismatch in localization files. The message key for "Changing offering for the volume..." was incorrectly named message.change.offering.processing and has been updated to message.change.offering.for.volume.processing to align with related message keys and its actual usage context.

Key Changes:

• Renamed message ID from message.change.offering.processing to message.change.offering.for.volume.processing in English localization
• Reordered Chinese localization entry to maintain consistent line numbering with the English file

Reviewed Changes

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

File	Description
ui/public/locales/en.json	Updated message key to include .for.volume suffix for consistency with related volume operation messages
ui/public/locales/zh_CN.json	Reordered message entry to align with English file structure

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 16.24%. Comparing base (ff0cfc9) to head (7055dca).
⚠️ Report is 2 commits behind head on 4.20.

Additional details and impacted files

@@            Coverage Diff            @@
##               4.20   #11890   +/-   ##
=========================================
  Coverage     16.24%   16.24%           
- Complexity    13396    13398    +2     
=========================================
  Files          5658     5658           
  Lines        499246   499246           
  Branches      60599    60599           
=========================================
+ Hits          81096    81100    +4     
+ Misses       409106   409102    -4     
  Partials       9044     9044           

Flag	Coverage Δ
uitests	4.03% <ø> (ø)
unittests	17.10% <ø> (+<0.01%)	⬆️

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.

[pavanaravapalli]

@DaanHoogland It's great to see the Telugu i18n for the Cloud Stack! I noticed a word where the translations aren't quite the right fit. It appears the system picked synonyms instead of the exact, intended word translations for those terms. Rule supposed to be 'నియమం' not 'పాలన' [ It means Govern ]. "ఎగ్రెస్ నియమం" is correct word :)

[DaanHoogland]

@pavanaravapalli , I only speak west-west-indo-european ;) so please feel free to add a PR to change it. I know of only one person involved in the Telugu translation so far and will ask him (@kiranchavala ) to review it.

[DaanHoogland]

(P.S. happy to play arbiter on your linguistic debates ;)

[abh1sar]

@sureshanaparti was it intended to have te.json in this change?
I think it is already present in 4.21

[DaanHoogland]

@sureshanaparti was it intended to have te.json in this change? I think it is already present in 4.21

@abh1sar , the reason I am including it is because the fix applies to it and will be overlooked otherwise. Happy to take it out and lay the maintenance burden on Telugu maintainers.

[abh1sar]

LGTM

[DaanHoogland]

@blueorangutan ui

[blueorangutan]

@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

[blueorangutan]

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/11890 (QA-JID-822)

[DaanHoogland]

@kiranchavala , can you have another look, please?

[DaanHoogland]

@kiranchavala , can you have another look, please?

@kiranchavala ping

[DaanHoogland]

@pavanaravapalli @kiranchavala @abh1sar , please ping me if you feel this must still go in. I feel that after some rebases, it no longer hold value (except for backporting the telugu