confirm sparsity failure with CRAN recipes

[simonpcouch]

main workflows GHA, currently with dev recipes, doesn't see an issue with sparsity that the CRAN version does see:

── Failure (test-sparsevctrs.R:219:3): toggle_sparsity changes auto to yes ────
extract_preprocessor(res)$steps[[1]]$sparse (`actual`) not identical to "yes" (`expected`).

`actual`:   "no" 
`expected`: "yes"

recipes 1.1.1 went to CRAN last week. It appears that sometime between a month ago and the recipes CRAN release, this workflows test was broken by recipes, and then since resolved on dev recipes in the last week. Just filing this PR to reproduce this on GHA.

[simonpcouch]

Oh, the newest CRAN recipes didn't introduce support for sparsevctrs. See dev NEWS

It's my sense, then, that there's no reason to send #283 to CRAN—the dev changes in workflows right now are almost all related to postprocessing and sparsevctrs, and I had been under the impression that this release was intended to enable sparse workflows.

[simonpcouch]

Alright, not an issue. This workflows release will still include sparsity stuff, but recipes patch just isn't triggering sparsity with auto quite yet: 800fb61

[github-actions]

This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.