[Storage] Delete Blob API responds not include header "x-ms-delete-type-permanent", which is not aligned with rest API doc

In [Rest API doc](https://learn.microsoft.com/en-us/rest/api/storageservices/delete-blob?tabs=azure-ad#response-headers), Delete Blob API responds will have "x-ms-delete-type-permanent" header for version 2017-07-29 and later.
Per my test, server will also return this header after 2017-07-29, no matter the account enable/disable soft delete.

But in [storage swagger](https://github.com/Azure/azure-rest-api-specs/blob/4a4fcbb05758711473d337c48541d75ef9283fe3/specification/storage/data-plane/Microsoft.BlobStorage/preview/2021-12-02/blob.json#L3624C25-L3624C36), the delete blob API responds not define the header "x-ms-delete-type-permanent".
This is not aligned with rest API doc and server behavior.

Currently , Azurite (storage rest API emulator) API is generated from swagger, since in swagger Delete Blob API responds not include header "x-ms-delete-type-permanent", Azurite also won't return it.
But Azure Storage Rust SDK is expecting the x-ms-deleted-type-permanent header and fails when this header is missing in the Azureite response.
So the swagger issue caused Azure Storage Rust SDK failed on Azurite. See https://github.com/Azure/Azurite/issues/2061/

Please fix swagger by adding the header to make it aligned with server behavior and rest API doc.

Start at specification/storage/data-plane/Microsoft.BlobStorage/preview/2021-12-02/blob.json around the Delete Blob response near line 3624. Compare its response headers with the linked REST API documentation and the reported server behavior. Done means the specification accurately declares x-ms-delete-type-permanent for the applicable API version.

Written by the indexing model from the issue text.