Fix Quarto build-deploy failure by restoring R toolchain in publish workflow

[Copilot]

build-deploy failed during Quarto publish when rendering Story_Telling/project1.qmd because Rscript was unavailable in the runner. This PR aligns the workflow with project requirements for mixed Python/R rendering and cleans up publish-step configuration.

• Workflow runtime requirements

  • Re-enabled R installation in .github/workflows/publish.yml (r-lib/actions/setup-r@v2).
  • Re-enabled R package install step (r-lib/actions/setup-r-dependencies@v2) for packages used by R code chunks (e.g., tidyverse, httr2, scales, knitr, DT).

• Publish step cleanup

  • Removed duplicate env mapping under the Quarto publish step to keep a single explicit GITHUB_TOKEN binding.

- name: Install R
  uses: r-lib/actions/setup-r@v2
  with:
    use-public-rspm: true

- name: Install R dependencies
  uses: r-lib/actions/setup-r-dependencies@v2
  with:
    packages: |
      any::tidyverse
      any::httr2
      any::scales
      any::knitr
      any::DT

[Copilot]

Pull request overview

This PR updates the Quarto publish GitHub Actions workflow to support mixed Python/R Quarto rendering (needed for Story_Telling/project1.qmd) and fixes the build-deploy workflow failure by ensuring the R toolchain is available during render/publish, while also cleaning up the publish step configuration.

Changes:

• Adds/ensures an R setup step (r-lib/actions/setup-r@v2) in the publish workflow.
• Adds/ensures an R dependency installation step (r-lib/actions/setup-r-dependencies@v2) for the packages used by R code chunks.
• Removes a duplicate env: mapping under the Quarto publish step so there is a single GITHUB_TOKEN binding.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.