Match BOM artifact to jenkins.version used

[alecharp]

In #632, the jenkins.version was bumped from 2.387.3 to 2.440.1 but the BOM was not. I discovered that during BOM release.

I cannot prove that this on its own would fix the BOM release.

Testing done

I ran mvn verify locally with no problem.

Proposed upgrade guidelines

N/A

Localizations

• [ ] English
• [ ] German
• [ ] French
• [ ] Slovak
• [ ] Czech
• [ ] ...

Submitter checklist

• [ ] The Jira / Github issue, if it exists, is well-described.
• [ ] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • The changelog generator for plugins uses the pull request title as the changelog entry.
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.
• [x] There is automated testing or an explanation that explains why this change has no tests.
• [ ] New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.