Upgrade to the latest version of commons-beanutils.

[jeffret-b]

Pick up the latest improvements and hardenings. Minor update. We don't use the affected features but it would be good to be on the latest version.

I don't think this one warrants a Jira ticket, but I can create one if it helps.

No new tests are needed as there should be no changes. Relying on existing tests and compilation for regression detection. The update from 1.9.3 to 1.9.4 should not have an impact.

See the commons-beanutils changelog or the PR

Proposed changelog entries

• Internal: Update commons-beanutils from 1.9.3 to 1.9.4.

Submitter checklist

• [n/a] JIRA issue is well described
• Changelog entry appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  * Use the Internal: prefix if the change has no user-visible impact (API, test frameworks, etc.)
• Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

[res0nance]

LGTM Assuming CI Passes

[Wadeck]

🐝 not tested manually, but read the changelog.

[jeffret-b]

Let's try a rebuild and see if we can get a clean one now.

[jeffret-b]

Hmm ... I need to investigate the test failures. See if they're because of my change or the Jenkins CI infra.

[jeffret-b]

This turned out to be more difficult than originally believed. The changes I proposed are insufficient and not necessarily the way we want to proceed. We should consider the technical debt of our Jelly release before proceeding in that direction.