[CI] Figure how to deal with laziness overhead #498
Description
For some generation tasks, the overhead from laziness can be tremendous (binary trees). This causes the Github Actions runners to run out of RAM. While this can be resolved by excluding particularly taxing examples when using laziness, it feels a bit unsatisfying.
Perhaps a more complete solution would be some user setting for capping laziness's memory usage. Once reached, further variables would be generated eagerly?
We could also reduce the sizes used in CI, since they are larger than necessary to all bugs we've seen. However, it is nice to see that our system scales.