feat(dependencies): Tracks Jenkins' three last LTS versions.

[gounthar]

In various parts of the documentation, we can see references to one or several Jenkins LTS versions, like in:

Link 1
Link 2
Link 3

Not all of them are consistent, and contributors, instead of bots, still maintain some.
There is already a Ruby script that helps with keeping the references up to date, but it does not address all the parts in the documentation.
As we are already using updatecli for other dependency updates, I propose to use it to keep track of the Jenkins LTS versions too.

I searched for PLACEHOLDER_RECENT_LTS_POINT_HIGHS, PLACEHOLDER_RECENT_LTS_POINT_HIGH, corebaseline, 2.401.3, 2.387, 2.375, and bom- to know what files I should make changes in, and only found four:

• https://github.com/jenkins-infra/jenkins.io/tree/master/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
• https://github.com/jenkins-infra/jenkins.io/tree/master/content/doc/developer/plugin-development/dependency-management.adoc
• https://github.com/jenkins-infra/jenkins.io/tree/master/content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc
• https://github.com/jenkins-infra/jenkins.io/tree/master/content/doc/developer/tutorial-improve/use-plugin-bill-of-materials.adoc

There is also this file that deals with Jenkins LTS versions, but it looks like it presents a fictional situation, so I'm not 100% sure this should be kept up to date.

I think this could be ameliorated, I'm not particularly proud of this manifest, but at least, it works.

For reference, this updatecli manifest has generated this PR on my fork of jenkins.io.

Bump last three Jenkins' LTS versions in the documentation

Bump Jenkins super old BOM artifact version in the "improve a plugin tutorial"

1 file(s) updated with "${1}1654.vcb_69d035fa_20${3}": * content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc

Bump Jenkins minimum BOM artifact in the "plugin-bill-of-materials" page

1 file(s) updated with "${1}bom-2.387.x${3}": * content/doc/developer/tutorial-improve/use-plugin-bill-of-materials.adoc

Bump Jenkins minimum BOM artifact version in the "plugin-bill-of-materials" page

1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}": * content/doc/developer/tutorial-improve/use-plugin-bill-of-materials.adoc

Bump Jenkins minimum BOM artifact version in the "improve a plugin tutorial"

1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}": * content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc

Bump Jenkins minimum LTS version in the recommended versions section

1 file(s) updated with "${1}2.401.3${3}": * content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc

Bump Jenkins good core dependencies LTS version in the recommended versions section

1 file(s) updated with "${1}2.387.3 and 2.401.3${3}": * content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc

Bump Jenkins latest LTS version in the recommended versions section

1 file(s) updated with "${1}2.414.2${3}": * content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc

Bump Jenkins minimum BOM artifact version in the "dependency management" page

1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}": * content/doc/developer/plugin-development/dependency-management.adoc

Bump Jenkins minimum LTS version in the "improve a plugin tutorial"

1 file(s) updated with "${1}2.401.3${3}": * content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc

Bump Jenkins minimum LTS version in the "improve a plugin tutorial task"

1 file(s) updated with "${1}2.401.3${3}": * content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc

Bump Jenkins minimum BOM artifact in the "dependency management" page

1 file(s) updated with "${1}bom-2.387.x${3}": * content/doc/developer/plugin-development/dependency-management.adoc

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[dduportal]

LGTM for the shell script + updatecli part but I would want a second pair of eye from the docs reviewer on the changed adoc content

##############################################################
# BUMP LAST THREE JENKINS' LTS VERSIONS IN THE DOCUMENTATION #
##############################################################


SOURCES
=======

JenkinsThirdToLastLTSTruncated
------------------------------
The shell 🐚 command "/bin/sh /tmp/updatecli/bin/96dd80dd757bf4c3c92aa37c45dff38f9479a4992b3bffd471bf469d2ac888ab.sh" ran successfully with the following output:
----
2.387
----
✔ shell command executed successfully

JenkinsTooOldToSucceedLTSTruncated
----------------------------------
The shell 🐚 command "/bin/sh /tmp/updatecli/bin/c6fece53fbb73ec2d8efaccb406ae2e6ad7fcfdf8850457680f8e75fff4441d8.sh" ran successfully with the following output:
----
2.319
----
✔ shell command executed successfully

BOM
---
✔ Latest version is 2465.va_e76ed7b_3061 on the Maven repository at https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/bom-2.387.x/maven-metadata.xml
--- content/doc/developer/plugin-development/dependency-management.adoc
+++ content/doc/developer/plugin-development/dependency-management.adoc
@@ -90,7 +90,7 @@
     <dependencies>
         <dependency>
             <groupId>io.jenkins.tools.bom</groupId>
-            <artifactId>bom-2.375.x</artifactId>
+            <artifactId>bom-2.387.x</artifactId>
             <!-- Latest version goes here -->
             <version>1981.v17df70e84a_a_1</version>
             <scope>import</scope>

```

⚠ - 1 file(s) updated with "${1}bom-2.387.x${3}":
	* content/doc/developer/plugin-development/dependency-management.adoc

setLTSVersionAsATask
--------------------

**Dry Run enabled**

"content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc" updated with [dry run] content "${1}2.401.3${3}"

```
--- content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc
+++ content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc
@@ -5,7 +5,7 @@
 
 :modified-files: pom.xml
 :task-identifier: require-newer-core
-:task-description: Require PLACEHOLDER_RECENT_LTS_POINT_HIGH as minimum Jenkins version
+:task-description: Require 2.401.3 as minimum Jenkins version
 
 = Update minimum Jenkins version
 

```

⚠ - 1 file(s) updated with "${1}2.401.3${3}":
	* content/doc/developer/tutorial-improve/update-base-jenkins-version.adoc

setSuperOldBOMBaseVersionInUpdateMinimumRequiredJenkinsVersion
--------------------------------------------------------------

**Dry Run enabled**

✔ - all contents from 'file' and 'files' combined already up to date

setJenkinsLatestLTSVersionInRecommendedVersions
-----------------------------------------------

**Dry Run enabled**

"content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc" updated with [dry run] content "${1}2.414.2${3}"

```
--- content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
+++ content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
@@ -38,7 +38,7 @@
 ## Currently recommended versions
 
 At the moment, the Jenkins releases *PLACEHOLDER_RECENT_LTS_POINT_HIGHS* make good core dependencies.
-You could also consider *PLACEHOLDER_NEWER_LTS_POINT_ONE* if there are specific reasons, like new features, to want something newer.
+You could also consider *2.414.2* if there are specific reasons, like new features, to want something newer.
 
 ## Changing the minimum required version
 

```

⚠ - 1 file(s) updated with "${1}2.414.2${3}":
	* content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc

setBOMVersionInDependencyManagement
-----------------------------------

**Dry Run enabled**

"content/doc/developer/plugin-development/dependency-management.adoc" updated with [dry run] content "${1}2465.va_e76ed7b_3061${3}"

```
--- content/doc/developer/plugin-development/dependency-management.adoc
+++ content/doc/developer/plugin-development/dependency-management.adoc
@@ -92,7 +92,7 @@
             <groupId>io.jenkins.tools.bom</groupId>
             <artifactId>bom-2.375.x</artifactId>
             <!-- Latest version goes here -->
-            <version>1981.v17df70e84a_a_1</version>
+            <version>2465.va_e76ed7b_3061</version>
             <scope>import</scope>
             <type>pom</type>
         </dependency>

```

⚠ - 1 file(s) updated with "${1}2465.va_e76ed7b_3061${3}":
	* content/doc/developer/plugin-development/dependency-management.adoc


ACTIONS
========

[Dry Run] An action of kind "github/pullrequest" is expected.

[NotMyFault]

The pages look much better now, thanks!

[dduportal]

Let's roll: we are 2 maintainers whom approved.