VM destroy API call returns unpredicted response

[OlegChuev]

problem

When I execute destroyVirtualMachine with expunge, I get an unexpected response:

{
  "null": {
    "securitygroup": [],
    "nic": [],
    "affinitygroup": [],
    "deleteprotection": false,
    "tags": []
  }
}

Instead of

{
  "virtualmachine": {
     // ...
  }
}

versions

4.20.1

The steps to reproduce the bug

1. Create VM
2. Destroy VM with destroyVirtualMachine with and without expunge
3. Check response

What to do about it?

Make response consistent for both requests

[sureshanaparti]

Fixed in #11352