Adds sketch of how to use pytest

[skrawcz]

This is a WIP. This shows how
one might log things they don't
want to fail on to a results_bag
and then access them in a dataframe...

Changes

How I tested this

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[github-actions]

A preview of 01c7e7c is uploaded and can be seen here:

✨ https://burr.dagworks.io/pull/442 ✨

Changes may take a few minutes to propagate. Since this is a preview of production, content with draft: true will not be rendered. The source is here: https://github.com/DAGWorks-Inc/burr/tree/gh-pages/pull/442/

[skrawcz]

TODO: show this:

E.g. run pytest, get dataframe of results (and do something with it), but also see traces for each of those runs in the Burr UI.