Add basic regression tests

A few implementations, specifically torch and libsvm/kernlab, don't have good control over random number usage. Also, we have seen differences in results across intel and apple silicon chips (but that seems to be getting better).

We have some places where we programmatically write out results in-line. If the results change, our encoded conclusions might no longer be valid.

We can take a few key objects and save their results once their usage is finalized. Then we can use testthat to verify that those results are the same (or within some tolerance). Since the project is almost structured like an R package, this means that we can use devtools::test() to check for consistency of results.

Start by reviewing the torch and libsvm/kernlab implementations and the existing places that write results inline. Use testthat through devtools::test() to identify key finalized objects, capture their results, and verify exact or tolerance-based consistency across supported chips. Done means regression tests cover the selected objects and guard against changed conclusions.