https://www.jenkins.io/doc/developer/plugin-development/dependency-management/#jenkins-core-bom says:

> Jenkins core provides a Maven Bill Of Materials (BOM) that centrally
> defines versions of various libraries used by Jenkins. If you are using
> Maven to build your plugin, then you can simplify dependency management
> by importing this BOM, at jenkins.version. Dependency versions are then
> automatically synchronized with the version of Jenkins against which
> you are building.

Since commons-beanutils is included in the Jenkins core BOM, we can
reference it as "provided" and since the Jenkins core BOM is now
included, we can rely on the Jenkisn core BOM to manage the version
of commons-beanutils.

That seemed to resolve the upper bounds dependency error and let me
learn more about the Jenkins core BOM.

Testing done:

* Tested with Jenkins 2.462.3 by creating a line plot that used a file
  named "plot-b.csv" with data that I added after each build.  The plot
  was shown correctly when the plot was defined in the freestyle project
  as a post build action.

* Tested with Jenkins 2.462.3 by creating a line plot as a build step
  and that failed with tip of the master branch and with the changes in
  this pull request.  I don't know if that is a recent failure or if it has
  been there a long time.  It has not been reported in the issue tracker.