downgrade Jenkins to 2.492.1

[jtnord]

As an API plugin with no other dependencies we should not be bumping the version and releasing. if a dependabot update for the version works then it can be closed.

per https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/

If you are packaging a pure API library (one that does not depend on Jenkins APIs) then you should ignore newer Jenkins versions and pick an older LTS

just pick a .1 and stick with it.

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[jtnord]

@jonesbusy could you take a look, TIA.