Move data download instructions to project directory setup

[JCSzamosi]

Closes #937.

Moves the instructions for downloading data from the Working with Data episode to the Introduction episode, to prevent disrupting the flow of the later lessons with technical glitches. Also clarifies the language about downloading data in the setup instructions.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/datacarpentry/R-ecology-lesson/compare/md-outputs..md-outputs-PR-939

The following changes were observed in the rendered markdown documents:

 ...-data-rendered-date-plot-challenge-answer-1.png | Bin 453296 -> 454177 bytes
 introduction-r-rstudio.md                          |   2 ++
 md5sum.txt                                         |   6 +++---
 setup.md                                           |   4 ++--
 working-with-data.md                               |   5 +----
 5 files changed, 8 insertions(+), 9 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-10-14 20:13:41 +0000

[CarolynKoehn]

I think this looks great! @datacarpentry/r-ecology-lesson-maintainers, could one of you give this a second look to make sure the changes look good to you?

[Bisaloo]

Thanks! I left some minor comments but it seems good to me 👍

[CarolynKoehn]

Thanks @JCSzamosi and @Bisaloo for working on this!