Update/clean images in the github_introduction lesson

[oharac]

In the github_introduction lesson, there are many many images that are effectively duplicated, mostly modifications by Sam - e.g., rstudio-commit-1.png and rstudio-commit-1-sam.png. We should decide on one vs. the other, or update the image entirely, but be consistent in any case.

In the script, there are many instances (example 1, example 2) where an older image is commented out - I suggest we just remove these lines!

[oharac]

Two other thoughts:

• if we are going in and touching all these image files, should we update the file naming convention for the images as well as in the script? here the file naming seems mostly in line with what @camilavargasp proposed in issue Lessons naming convention #1 with the exception of mixed kebab-case and snake-case.
  • if we wanted to automate this somewhat, it would be easy to use tolower() and str_replace_all() to rename all the files
  • ...but we'd still need to manually fix these inside the .qmds
• Some of the image files are quite large (e.g, 3 MB for Allison's Git workflow drawing - it is 3800 pixels square, for our purposes we could dramatically reduce the resolution (e.g., to 1080x1080 pixels) and still have it show up great in the rendered book.
  • this again could be something automated, using the magick package
  • for each image, if it's above a certain file size, read it in to magick, reduce the max size to some good value (like 1080p)

[oharac]

one more: Quarto seems to prefer the pandoc image format ![text](image_url){options} so as we clean up lessons, convert knitr::includes to this kind of format

[camilavargasp]

These all sound good to me!

• I vote yes for streamlining names. Eventually, we should do a lesson review to ensure we remove unnecessary comments, update images if necessary, and so on.
• About the different versions of the images I tried to transfer only Sam's version to the coreRlessons to avoid duplicates. In the future we should decide to either stick to one person(username), or recreate the images with a generic username.