Storage: After recreating a storage account with the same name, the data plane API will not work

## Steps to reproduce

Delete an existing storage account:

```
DELETE /subscriptions/xxxx/resourceGroups/acctestRG-220715151131118951/providers/Microsoft.Storage/storageAccounts/unlikely23exst2acctcok4n?api-version=2021-04-01
```

Create the same named storage account:

```
PUT /subscriptions/xxxx/resourceGroups/acctestRG-220715151131118951/providers/Microsoft.Storage/storageAccounts/unlikely23exst2acctcok4n?api-version=2021-04-01
```

Poll until the LRO finishes:

```
GET /subscriptions/xxxx/providers/Microsoft.Storage/locations/westeurope/asyncoperations/ceb3878b-43fd-408b-a1c8-ae168cc99868?monitor=true&api-version=2021-04-01
```

Access the data plane API:

```
GET https://unlikely23exst2acctcok4n.queue.core.windows.net/?comp=properties&restype=service

Response 404

b'\xef\xbb\xbfResourceNotFoundThe specified resource does not exist.\nRequestId:40047022-8003-0062-7e1a-986d0e000000\nTime:2022-07-15T07:16:53.6322014Z'
```

Same for the blob:

```
GET https://unlikely23exst2acctcok4n.blob.core.windows.net/?comp=properties&restype=service

Response 404

b'\xef\xbb\xbfResourceNotFoundThe specified resource does not exist.\nRequestId:a44689b6-d01e-0032-3d1a-98af5e000000\nTime:2022-07-15T07:16:54.1791841Z'
```

No repository file or test is named. Start by reproducing the delete-and-recreate sequence and checking the Azure Storage management, queue, and blob endpoints; done means the relevant REST specification or issue scope explains and covers successful data-plane access after recreation.

Written by the indexing model from the issue text.