container-specific considerations

[willow-ahrens]

Adds a section on container-specific considerations for Binsparse.
Asking for help:

• @BenBrock I think we might want to add some language about datatypes in HDF5, is that right?
• @hameerabbasi Could you add a section on in-memory considerations, or at least a link?
• @ivirshup Do you agree with the way I've laid out npy files? npz files are a little messier to work with so I didn't use them, but if you think that's the more correct way to go I'd like to hear your feedback. Also, do you think you'd like to add a section on zarr?

[github-actions]

Automated Review URLs

• render latest/index.bs

[willow-ahrens]

https://github.com/orgs/zarr-conventions/repositories

[BenBrock]

On types for HDF5, we should probably have a table mapping the Binsparse types to HDF5 types. The current canonical mapping is here in the C implementation.

There are other mappings that would be reasonable (basically the big endian versions of all these). If we want to allow those, we could list the big endian and little endian HDF5 standard types side-by-side, or just say it needs to be read in as, e.g., a 64-bit integer type.