Create a community structure for sharing VirtualiZarr workflows and Icechunk virtual stores / Kerchunk references

[maxrjones]

Many Kerchunk workflows were developed as one-off Jupyter Notebooks that were shared on as a GitHub Gist or at most Medium blog posts/conference presentations. While all these examples were fantastic, it was often difficult to find examples and understand their differences. https://github.com/ProjectPythia/kerchunk-cookbook provided a more consistent structure, but was built after the fact by a small number of people. I think it would be valuable to promote a structure for sharing VirtualiZarr workflows earlier in process, so that they are open, findable, and ideally consistently structured. I also think there's a lot to learn from STAC in this type of community organization and would like to propose mirroring the stactools-packages structure. In this model, we would:

• Create a Virtual-Zarr GitHub organization, akin to https://github.com/stactools-packages
• Create a template repository, akin to https://github.com/stactools-packages/template (xref Develop a cookiecutter template for virtualization #319)
• Create a method for people to transfer their repositories to https://github.com/virtual-zarr
• Create a landing page for Virtual Zarr datasets, akin to https://stactools-packages.github.io/

I think it would be great if we had a way for people to easily clone their virtual data stores to a publicly accessible location (to my knowledge this isn't in place for STAC). IIRC @norlandrhagen suggested source.coop as a potential hub for sharing the actual virtual stores.

[norlandrhagen]

@maxrjones I just stumbled across https://github.com/stac-utils/xstac/tree/main. They have examples using Kerchunk references to create STAC assets.