[R] Create a CRAN-specific packaging checklist that lives in the R package directory

[asfimport]

Like other packaging tasks, the CRAN packaging task (which is concerned with making sure the R package from the Arrow release complies with CRAN policies) for the R package is slightly different than the overall Arrow release task for the R package. For example, we often push patch-patch releases if the two-week window we get to "safely retain the package on CRAN" does not line up with a release vote. @nealrichardson has heroically been doing this for a long time, and while he has equally heroically volunteered to keep doing it, I am hoping to process of codifying this somewhere in the R repo will help a wider set of contributors understand the process (even if it was already documented elsewhere!).

@stephhazlitt and I use usethis::use_release_issue() to manage our personal R package releases, and I'm wondering if creating a similar function or markdown template would help here.

I'm happy to start the process of putting a PR up for discussion!

Reporter: Dewey Dunnington / @paleolimbot
Assignee: Dewey Dunnington / @paleolimbot

PRs and other links:

• GitHub Pull Request #14678

_{Note: This issue was originally created as ARROW-18345. Please see the migration documentation for further details.}

[asfimport]

Neal Richardson / @nealrichardson:
I've been keeping https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRpackages up to date. The only thing not mentioned there is that I generally make a branch on my fork off of the release tag (apache-arrow-x.y.z) where I add/cherry-pick any extra commits we need for the CRAN release. Sometimes this is just deleting the line in the README with the badges to avoid spurious URL check failures.

The other thing not mentioned there, now that I look at it, is doing reverse dependency checks.

[asfimport]

Dewey Dunnington / @paleolimbot:
Issue resolved by pull request 14678
#14678