Main2Dev @W-22462048@ Merging main to dev after v5.15.0

[svc-cli-bot]

This branch and PR were automatically created following the successful release of v5.15.0.
It must be MERGED into dev, NOT SQUASHED OR REBASED. Squashing or rebasing this branch onto dev can cause potentially irreconcilable merge conflicts later.
As an additional safeguard and reminder, the title of this PR MUST include the word 'merging' in the description portion of the PR title, e.g., 'Main2Dev @W-XXXXXXX@ Merging main to dev after vX.Y.Z'.
If there are conflicts between dev and this branch, you should do the following locally:

• $ git checkout dev
• $ git pull
• $ git fetch --all
• $ git checkout m2d/v5.15.0
• $ git pull origin dev --no-rebase # You MUST include this flag, or someone's day will be ruined.
• Resolve the merge conflicts manually. When in doubt, ask the code's author for help.
• $ git commit
• $ git push

[aruntyagiTutu]

Content check: diff is exactly the expected Main2Dev merge — only the version bump (5.14.0→5.15.0) in package.json/package-lock.json, carrying in the already-reviewed v5.15.0 release commit from #2071. No unexpected changes.

Non-blocking process note: per this PR's own description, the title must include the word 'merging' (e.g., 'Main2Dev @W-XXXXXXX@ Merging main to dev after v5.15.0') before merging, and it's still the default 'Filler title. Read description and rename.' Please rename before merge — also flagging that this PR must be merged (not squashed/rebased) per the same instructions.

[aruntyagiTutu]

Title has been renamed to include "Merging" per the Main2Dev requirements, and mergeable status is now MERGEABLE. Diff is just the version-bump carry-in (package.json/package-lock.json 5.14.0 → 5.15.0) from the already-reviewed #2071 release. Approving — please merge (not squash/rebase) per the PR description.

[nikhil-mittal-165]

approved