MAINT: stable -> latest xrefs on main (#167)

Author: lizgehret

book/plugins/how-to-guides/set-up-development-environment.md

@@ -99,7 +99,7 @@ Config Source: /Users/q2-user/miniforge3/envs/q2dev-tiny-2025-04-30/etc/qiime2_c
 
 Getting help
 To find help and learning resources, visit https://qiime2.org.
-To get help with configuring and/or understanding QIIME 2 parallelization, visit https://use.qiime2.org/en/stable/references/parallel-configuration.html
+To get help with configuring and/or understanding QIIME 2 parallelization, visit https://use.qiime2.org/en/latest/references/parallel-configuration.html
 ```
 
 The versions listed here, for QIIME 2, q2cli, q2-types, and q2-metadata are development versions as defined by [versioneer](https://github.com/python-versioneer/python-versioneer), and these indicate that you're working in a QIIME 2 development environment (as opposed to working with a specific release version of QIIME 2).

book/plugins/tutorials/add-parallel-pipeline.md

@@ -269,7 +269,7 @@ las_results, = combine_action(las_results)
 
 Under the hood is where the magic happens here.
 Because we're iterating over a collection of QIIME 2 Artifacts (the `for` loop above) in a QIIME 2 `Pipeline`, each `las_result` object is a proxy for a real QIIME 2 artifact.
-The jobs to create them are distributed as indicated in the user's [QIIME 2 parallel configuration](https://use.qiime2.org/en/stable/references/parallel-configuration.html).
+The jobs to create them are distributed as indicated in the user's [QIIME 2 parallel configuration](https://use.qiime2.org/en/latest/references/parallel-configuration.html).
 The code continues executing as if these were real Artifacts, not proxy Artifacts, until something is needed from them.
 At that point, the code will block (i.e., wait) until the proxy Artifacts become real Artifacts, and then continue processing.
 

book/plugins/tutorials/create-from-template.md

@@ -74,7 +74,7 @@ Miscellaneous:
   --help                  Show this message and exit.
 ```
 
-If you'd like to try the action out, you can call your `duplicate-table` action on any QIIME 2 `FeatureTable[Frequency]` artifact (e.g., you can download one from the QIIME 2 user documentation with [this link](https://gut-to-soil-tutorial.readthedocs.io/en/stable/data/gut-to-soil/asv-table.qza)).
+If you'd like to try the action out, you can call your `duplicate-table` action on any QIIME 2 `FeatureTable[Frequency]` artifact (e.g., you can download one from the QIIME 2 user documentation with [this link](https://gut-to-soil-tutorial.readthedocs.io/en/latest/data/gut-to-soil/asv-table.qza)).
 Load your duplicated table with [QIIME 2 View](https://view.qiime2.org), and poke through its Provenance to see how data provenance is recorded for your plugin.
 
 ## Initialize a git repository (optional but recommended)