ENH: get timing info for notebooks/cells

[bsipocz]

Currently, we don't use pytest, but it would be nice to find a way to run --durations type stats on the notebooks with nb execution, too. It would help to pin down bottlenecks such as #324

[bsipocz]

Note there is: https://myst-nb.readthedocs.io/en/latest/computation/execute.html#execution-statistics, we just need to figure but it doesn't go into the cell level detail as pytest do; and the notebook level timing info is already in the log (though of course having a nicely rendered table could be useful, too)

[jkrick]

We had also talked about having the notebook timing info as a part of the intro to the notebooks so users would know how long to expect the notebook to take to run. Is this info, from either myst or pytest, able to be fed back into the text? Or is that dreaming?

[bsipocz]

This is more about ci and benchmarking on the code cell level, but actual user expected FSC timing info somewhere in the top description would be nice, too.

[bsipocz]

Is this info, from either myst or pytest, able to be fed back into the text? Or is that dreaming?

The total runtime can be easily harvested from the logs, see the link above for an example, but I don't think that would be particularly useful for the users as the resources we use in CI are much different, especially as we're thinking about stupidifying some of the cells for CI.

[jkrick]

good point about different resources.