snap changes with additional warning context on R-devel

[simonpcouch]

On main dev version, a number of snap changes in GHA where the header for warnings includes context. Only occurs on R-devel:

-   Warning:
+   Warning in `p_value()`:

[simonpcouch]

Strangely, the infer CRAN check page lists an error on one devel system, but it's a different result (which seems to list no actual error) and I haven't received an email about it.

Version: 1.0.6
Check: tests
Result: ERROR 
    Running 'testthat.R' [188s]
  Running the tests in 'tests/testthat.R' failed.
  Complete output:
    > # This file is part of the standard setup for testthat.
    > # It is recommended that you do not modify it.
    > #
    > # Where should you do additional test configuration?
    > # Learn more about the roles of various files in:
    > # * https://r-pkgs.org/tests.html
    > # * https://testthat.r-lib.org/reference/test_package.html#special-files
    > 
    > library(testthat)
    > library(infer)
    > 
    > test_check("infer")
    [ FAIL 0 | WARN 4 | SKIP 108 | PASS 349 ]
    
    ══ Skipped tests (108) ═════════════════════════════════════════════════════════
    • On CRAN (108): 'test-aliases.R:14:3', [...truncated...]
    
    [ FAIL 0 | WARN 4 | SKIP 108 | PASS 349 ]
    Deleting unused snapshots:
    • shade_confidence_interval/ci-both-fill.svg
    • shade_confidence_interval/ci-both-nofill.svg
    • [...truncated...]
    > 
    > proc.time()
       user  system elapsed 
      29.42    1.90   31.34
Flavor: [r-devel-windows-x86_64](https://www.r-project.org/nosvn/R.check/r-devel-windows-x86_64/infer-00check.html)

[simonpcouch]

^^^ is the case for many packages at the moment. Ignoring.

[simonpcouch]

Due to changes in base R .Deprecated(). Transitioning to lifecycle so that we get version-stable results. Advancing conf_int() and p_value() deprecations to deprecate_stop(), as these have been deprecated since #181.

[github-actions]

This issue 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.