Upgrade 3rd party dependencies (Q3 2023)

[gmartinez3werfen]

PR Details

Updates dependencies for the following libraries:

• jasperreports (6.17.0 --> 6.20.6)
• jasperreports-fonts (6.17.0 --> 6.20.6)
• lombok (1.18.12 --> 1.18.30)
• poi (5.1.0 --> 5.2.4)
• poi-ooxml (5.1.0 --> 5.2.4)
• junit-jupiter-api (5.3.2 --> 5.10.0)
• junit-jupiter-engine (5.3.2 --> 5.10.0)
• java-report-test-utilities (1.2.0 --> 1.3.0)

Motivation and Context

This change is required by Cybersecurity team in order to keep dependencies updated for reducing surface attack caused by known vulnerabilities.

Implementation

Updated pom.xml versions for dependencies to the latest available.

How Has This Been Tested

All existing tests were ran without any issue.

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New release version
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the CONTRIBUTING document
• My code follows the code style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• There are component tests for new/changed code (or a good explanation why this was not possible) and all of them passed. I have also added tests to cover my changes
• All CI builders have indicated success (Give them the needed time to notice the pull request)
• The Pull request title has the type of change ended with a slash (bugfix/feature/...), Jira issue numbers separated by spaces (if any), a space, and then a short, but descriptive summary
• Commit messages are well formed: A note about Git commit messages
• New public packages, classes, and methods are documented. (Strongly consider documenting private classes and methods)
• A new branch needs to be created from master to evolve previous versions
• Increase version in pom.xml following Semantic Versioning
• Squash merge as a recommended merge strategy in Bitbucket

[QuimNotoTrilla]

Good be updated

[joaquimvila]

I miss linking this PR with the issue #28, so when closing it, the issue should be closed too.