R Packages text when no renv.lock file exists

[kgartland-rstudio]

I think this was placeholder text when we didn't have a Scan button for the R Packages.

To deploy R content, you need a package file listing any package dependencies, but the file does not exist or is invalid. Use 'renv::snapshot()' at an R console to create one or edit the current configuration file (configuration-1) to point to an existing valid file.

Should we instead be asking the user to hit the Scan button here?

[mmarchetti]

We should recommend clicking the big blue button, or running renv::snapshot() (or maybe renv::init()).

[mmarchetti]

Also see #1745

[jonkeane]

I'm bumping this out of the 1.2 release, but we should come back to it. Making sure we have a good experience for someone coming fresh and not familiar with renv is on us to make sure they have an easy onboarding (since we require they use it). Same for #1745

[dotNomad]

With the work that @marcosnav did on the no renv or renv.lock cases in #2560 the deploy prompts help a lot with renv.

The R Packages section still needs some work. It recommends looking at the renv documentation right now:

However this issue is a bit stale - @marcosnav created a follow-up issue to provide the same helpful prompts we offer during deployment to the R Packages section #2565. I believe that issue captures the intention behind this one.