Bump to 0.0.6 to trigger release

[joshmoore]

There are apparently cases where release: [created] leads to the deploy not being triggered. Attempting an expansion to [created, published].

cc: @brokkoli71 @normanrz @dominikl

[sbesson]

Alternatively, the deploy workflow could be triggered on a tag with a final step creating the GitHub release using the gh release create CLI

[joshmoore]

nods. Happy to go with that as well, but I thought this smaller change would help to pinpoint if my guess about "created" is true.

Do you have a repo, @sbesson, that you think of as the "mvn central deployment template"?

[sbesson]

On the OME side, all these Maven repositories have been updated to deploy to Central - https://ome-contributing.readthedocs.io/en/latest/java-development.html and can be used as starting points

[joshmoore]

Ok. Got a 👍 from @normanrz on this so I'm going to push ahead with 0.0.6 as a test of the release mechanism, and then we can move to something tag-based for the next release.

[joshmoore]

👍

[joshmoore]

Unfortunately there is currently a test failure -- #41