chore(dependencies): Separate LTS and BOM versions updatecli manifests

[gounthar]

Up to now, we have been using one manifest to update the Jenkins LTS versions in various parts of the documentation simultaneously with the BOM versions.
In some cases, the title was quite clear, such as:

Bump Jenkins LTS versions to 2.414.2 in various parts of the documentation

and accurately reflected the update to this version. However...
In other instances, the title was:

Bump Jenkins LTS versions to 2.414.3 in various parts of the documentation

and it created confusion as we were only updating the BOM version... This issue was highlighted here.

Therefore, I propose having two separate manifests, leading to two distinct PRs (which may or may not occur simultaneously): one for the Jenkins LTS versions and another for the plugin bill of materials versions.

The PR titles would be such as:

• Update the plugin bill of materials versions to 2507.vcb_18c56b_f57c in various parts of the documentation
• Update Jenkins LTS versions to 2.414.3 in various parts of the documentation

Please have a look at two generated PRs on my fork:

• Update the plugin bill of materials versions to 2507.vcb_18c56b_f57c in various parts of the documentation gounthar/jenkins.io#44
• Update Jenkins LTS versions to 2.414.3 in various parts of the documentation gounthar/jenkins.io#45

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[kmartens27]

Thanks very much for the work on this @gounthar !

[dduportal]

nitpick on the title: this must be a chore as merging this PR does not add anything the "artifact produced and consumed by the repository" (e.g. jenkins.io website), but it adds something to a transversal subsystem not consumed directly by end-users