Fix of example in Set-AzDiskKeyEncryptionKey and Set-AzDiskDiskEncryptionKey

[simonesavi]

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

In the description of cmdlets Set-AzDiskKeyEncryptionKey and Set-AzDiskDiskEncryptionKey there is an example that, in case of disk restore, work well during the OS disk restore.

In case this operation will be done to restore a data disk, during the attachment of data disk to VM, the operation fail.
In order to fix this, an analysis was done with product group team. The outcome is that disk configuration must have a parameter that must be set in order to have data disk fully recovered.

I have tested the configuration for both OS and data disk, and it works without problem. For this configuration could be considered generic.

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

Release branch for 2020-02-18 was already cut yesterday, In order to catch the release, cherry picked your commits in to another pr: #11108