feature: polaris fsspec write implementation

[lmtroper]

Changelogs

Integrated a basic write implementation for Zarr files with the Polaris FSSpec. Some of the major changes include:

• Added a new endpoint in the client to be able to write a zarr file of a Polaris dataset.
• Added two new methods in the FSSpec: rm and pipe_file

More details of the FSSpec Implementation:

• The rm method is currently added as placeholder since it's required for the Zarr writing integration.
• The pipe_file method calls the hub to get a signed URL for a PUT request, then writes the data to the bucket. The S3 bucket uses SHA-256 for data security but it is currently set to None.

---

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.
• 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 or test (or ask a maintainer to do it for you).

---

[cwognum]

This look great already! Thank you for taking the time to document everything! 🙏

For the failing code checks, it seems there is a mismatch between the line length we expect and the line length used. This should be automatic, as it is configured in the pyproject.toml. After navigating to the root directory, you should be able to just run:

ruff format .

It is a little weird though, because the error message states:

Would reformat: polaris/hub/client.py
Would reformat: polaris/utils/types.py
2 files would be reformatted, 43 files already formatted
Error: Process completed with exit code 1.

But types.py is fine for me locally. Let's try again and I'll look into it some more if it's not fixed.

[cwognum]

Thanks @lmtroper ! Almost there!

[cwognum]

Very polished! 💅

One minor comment still, but this is great work! Thank you @lmtroper !

[cwognum]

Feel free to merge this PR whenever you're ready! 🙏