Only adding zarrRootPath field to datasets that use Zarr

[Andrewq11]

Changelogs

Updating the client.upload_dataset method to only add the zarrRootPath field to datasets which make use of Zarr. Otherwise, datasets which do not use make use of Zarr will fail a validation check and cannot be uploaded.

---

Checklist:

- [ ] Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
- [ ] Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).

• Update the API documentation if a new function is added, or an existing one is deleted.
• Write concise and explanatory changelogs above.
• If possible, assign one of the following labels to the PR: feature, fix, chore, documentation or test (or ask a maintainer to do it for you).

---

discussion related to that PR

[cwognum]

I'm okay with merging this to unblock everyone, but this piece of code feels brittle to me (my bad!).

Maybe we should instead improve the check on the Hub side to use the usesZarr field? This is already part of the payload anyways. And maybe the Hub should actually create and return a zarrRootPath to upload to? Something to think about!

[Andrewq11]

I'll merge this and create a ticket to improve how we handle validation on the Hub side when it comes to Zarr datasets.