WIP: [ci] [R-package] re-enable 'rchk' checks

[jameslamb]

Replaces #6332

#6266 and related PRs mad project's shell scripts stricter, so they now exit with a non-0 exit code the first time anything goes wrong (e.g. some variable they require isn't set or some command they run fails).

That work revealed that the CI job supposed to be checking the R package with rchck has not actually been working!

That job currently prints this:

/__w/LightGBM/LightGBM/.ci/test_r_package.sh: line 178: docker: command not found

And then just exits "successfully" with an exit code of 0 🙃

(link to recent build from master)

I suspect that that's been silently broken for over a year... since #5638. That PR moved all of the Linux R-package jobs inside of containers, but the ubuntu:latest image doesn't have docker in it and isn't set up for docker-in-docker by default. Following the docs in https://github.com/kalibera/rchk/blob/master/doc/DOCKER.md, that job expects to build the R package on the host, then docker run a container with rchk in it and that package mounted in.

This PR proposes the following:

• using the new R-hub images for rchk (similar to [ci] [R-package] add CI jobs covering more CRAN "additional checks", fix R_NO_REMAP warnings (fixes #6369) #6523)
• removing rchk-specific branches and special conditions in other CI scripts

Benefits of these changes

• restores a CI job that can be used to catch issues with the R package which otherwise wouldn't be caught until an attempted release to CRAN
• simplifies the script used by most macOS and Linux R-package CI jobs in the project

How I tested this

Intentionally pushed a change that would create an imbalance of PROTECT() / UNPROTECT() calls in lightgbm_R.cpp. Saw this check fail as expected.

([build link]())

Then reverted that and saw it passing on this branch.

References

The rchk job was first added here in #4449.

CRAN rchk check description: https://raw.githubusercontent.com/kalibera/cran-checks/master/rchk/README.txt (linked from https://cran.r-project.org/web/checks/check_issue_kinds.html).