Update Jenkins LTS versions to 2.479.1 in various parts of the docume…

…ntation (#7667)

chore: Bump Jenkins oldest weekly supported version in the "Choosing ...

... a version" page

Made with ❤️️ by updatecli

Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com>

content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc

@@ -13,7 +13,7 @@ You need to balance compatibility and features:
 In particular, the LTS Release Line is based on slightly older releases to provide a more stable experience for conservative users.
 * *Building against recent Jenkins versions* allows you to use recently added core features and API from your plugin. 
 You will also use that newer version for `mvn hpi:run`, so it may be easier to test your plugin with newer Jenkins releases. 
-* *Do not use versions no longer supported by the update center*, which is currently anything older than 2.425 for weekly releases, and 2.414.2 for LTS releases.
+* *Do not use versions no longer supported by the update center*, which is currently anything older than 2.426 for weekly releases, and 2.414.2 for LTS releases.
   Note that the lowest supported version changes about every week (weekly release) or every month (LTS release), so these specific versions will be a bad choice soon.
 * *Prefer an LTS version over weekly versions.*
 ** If you are based on the _currently active_ LTS line,