Add a notebook demonstrating the workflow for looking up scene traceability metadata for ARPS

[tbarsballe]

Recently, the BYOC API added the capability to download files
This allows users to read the scene traceability metadata header of ARPS tiles and map index values the corresponding band of the QA asset to scene ids, which was previously impossible for collections hosted on the Planet Insights Platform.
To do this in the most efficient manner, it is possible to read only the header of the tile, rather than downloading the whole file; this approach is demonstrated in this notebook.

While the example demonstrated here relates to ARPS, the general approach is applicable to other data sources as well, such as Fusion.

[leo-schmidt]

Sadly I did not have an ARPS collection at hand to test this directly, but the notebook is easy to read and follow throughout.
Nice job!
I just left some suggestions for small improvements in readability. The suggestions were a bit hard to do in the notebook diffs, I hope you can read them well.

[matthew-ballard]

This is great! Just one comment - I wonder if this would better in it's own folder within workflows, or within a new api_guides folder for byoc_api. I think that introduction-to-analysis-apis is just one topic rather than a collection of topics.

[tbarsballe]

This is great! Just one comment - I wonder if this would better in it's own folder within workflows, or within a new api_guides folder for byoc_api. I think that introduction-to-analysis-apis is just one topic rather than a collection of topics.

@matthew-ballard - I had quite a bit of trouble determining where to put this, and kinda just crammed it in here, I'm certainly open to moving it. However, I'm not certain a dedicated byoc API section is the right place

• It primarily concerns ARPS, so could go in an ARPS section (which we don't really have)
• It utilizes the Statistical, Catalog, and BYOC APIs, in roughly equal measures. The only reason BYOC is especially notable is because it's demonstrating a new feature of that API.

Let me know what you think...

[matthew-ballard]

I think then I would say it's own folder within workflows might make sense then