Update ChangeLog for DataProtection

[vidai-msft]

Added support for Data Protection Platform vault soft delete feature in the upcoming release.

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull request overview

This pull request adds a changelog entry for the upcoming release that documents the addition of vault soft delete functionality in the Azure Data Protection module. The change is specifically for documentation purposes to inform users about a new feature.

Changes:

• Added a single changelog entry under "## Upcoming Release" section documenting support for vault soft delete feature

[Copilot]

This changelog entry lacks sufficient detail for Azure PowerShell users. According to the ChangeLog guidelines:

1. Missing GitHub issue reference: The entry should reference related GitHub issues when applicable (e.g., "[[Do not Squash][Storage] Merge latest change from master to storage preview branch #12345]")

2. Insufficient user context: The entry should explain what the feature means for users and how it impacts their usage, not just state that it was added.

3. Missing implementation details: Similar entries in this file include sub-bullets with additional context, such as which cmdlets were added or modified. For example, this vault soft delete feature appears to involve cmdlets like 'Undo-AzDataProtectionVaultDeletion' and 'Search-AzDataProtectionSoftDeletedVaultBackupInstanceInAzGraph'.

Consider revising to follow the pattern seen in Version 2.1.0 (line 54) which says "Added soft delete and MUA feature for Backup vaults" or Version 2.4.0 (line 45) which provides specific cmdlet names. The entry should include sub-bullets explaining what users can now do with this feature (e.g., undelete vaults, search for soft deleted instances).