Bump version to 0.0.4

[sbesson]

In preparation of a release of zarr-java with the latest sharding improvements in #6 and #7. See #7 (comment) for issues with the 0.0.3 tag.

Proposing to tag a 0.0.4 release. Alternatively, we could delete the existing 0.0.3 tag (which artifacts never got promoted) and re-release 0.0.3

[sbesson]

From my reading of https://central.sonatype.org/publish/release/#close-and-drop-or-release-your-staging-repository, I suspect that once a tag has been pushed, the GitHub workflow will create and deploy a new set of artifacts in a staging repository on OSSRH.
There might still be a manual step for promoting these artifacts to the Central Repository which requires the person authenticated via

zarr-java/.github/workflows/deploy.yml

Lines 56 to 57 in e3e2208

	MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
	MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}

to log into the UI (in that case @joshmoore I believe)

[joshmoore]

Ready when you guys are, I'd just suggest creating the tag via a Release since that appears to be what I did last time.

[joshmoore]

Release triggered (and note: there was another 0.0.2 release on sonotype.org which I "dropped")

[sbesson]

https://repo1.maven.org/maven2/dev/zarr/zarr-java/0.0.4/ 🚀

[joshmoore]

I ran across some statistics while looking for a way to migrate ownership of this namespaces