changing path of a zarr asset does not change original association of uploaded zarr

this is a fairly critical bug since i renamed every single ngff file in the archive. especially since we currently have a one to one mapping between zarr id and asset, this should not have happened. alternatively, it should store multiple associations.

here is the updated asset with the `.ome.zarr` extension

https://api.dandiarchive.org/api/dandisets/000108/versions/draft/assets/044dfda2-1bef-414a-8e8c-1e5118ffe6e7/

but doing this still returns the old name

```
curl -X GET "https://api.dandiarchive.org/api/zarr/15662576-2df1-4035-a37e-b9f74fd5cb5b/" -H "accept: application/json"
```

response

```json
{
"name": "sub-MITU01/ses-20210521h17m17s06/micr/sub-MITU01_ses-20210521h17m17s06_sample-178_stain-NN_run-1_chunk-3_SPIM.ngff",
"dandiset": "000108",
"zarr_id": "15662576-2df1-4035-a37e-b9f74fd5cb5b",
"status": "Complete",
"checksum": "a97bf63ac294436d65e6d86eba657994-37481--14599540180",
"upload_in_progress": false,
"file_count": 37481,
"size": 14599540180
}
```

Reproduce the issue with the linked asset endpoint and the Zarr API request for zarr_id 15662576-2df1-4035-a37e-b9f74fd5cb5b. Trace how the Zarr record and uploaded asset association are updated when the asset path changes; done means the API returns the updated .ome.zarr name or correctly exposes all associations.

Written by the indexing model from the issue text.