Minor suggestions from using automate-testing and facilitate-installation

[cherman2]

This was honestly so straight forward and made setting up testing and installing for q2-fmt a breeze. 🥇

Here are a couple things that I had some questions on:

• We explain were the github action files go after we explain how to make the file, if we put that before it will enable uses to make the file in the right place without bouncing around our guide.
• Adding a name suggestion for the cron file might helpful. @lizgehret and I talked about cron- "plugin-name".yml
• It might be good to mention "passed" builds for the env file, that way people can be testing on our most recent prepare. (for me I am using it because q2-fmt depends on q2-stats which is in amplicon-2024.5)

I think this is going to be SO helpful for community plugin developers! This was so easy to follow.