4. Stretch: Provide bearer-token HTTP support in Icechunk

[maxrjones]

[maxrjones]

I converted this to an issue to:

1. record a recommendation in slack from @kylebarron to consider letting icechunk python take in a protocol (based on obspec) so that you can use obstore for it, but you can also manage some custom client as long as you implement the core methods icechunk needs
2. make it more visible that this issue is up for grabs. PO.DAAC routinely asks for it, so it'd be high-impact. I think we'd all be leaning heavily on AI assistance here, so people should feel welcome to jump in. Tom welcomed claude-assisted PRs in Icechunk

[kylebarron]

In related work, I made earth-mover/icechunk#2160, which prototypes passing obstore stores into icechunk. This implementation is a bit... hacky? in the sense that it tries to extract the config from an obstore store and convert the parameters into something that icechunk natively implements.

Alternatively I could prototype icechunk python support for obspec. In theory all icechunk needs is obspec-compliant + pickle-able. That would mean Icechunk would implicitly support all functionality of obstore, with the downside that requests have to go through Python.

[kylebarron]

I added a comment here: earth-mover/icechunk#1632 (comment) with the above information.

I can't really do anything until someone from earthmover comments on what approach they'd accept.