chore: Upgrade v1 dependencies

[taban03]

Description

Upgrade v1 dependencies

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[pj892031]

We can also upgrade those:

commonsLang3Version = '3.14.0'
commonsTextVersion = '1.12.0'
commonsIoVersion = '2.16.1
gsonVersion = '2.10.1'
guavaVersion = '33.1.0-jre'
janinoVersion = '3.1.12'
jsonSmartVersion = '2.5.1'
jsonVersion = '20240205'
lettuceVersion = '6.3.2.RELEASE'
lombokVersion = '1.18.32'
nettyVersion = '4.1.109.Final'
swagger3CoreVersion = '2.2.21'
swagger3ParserVersion = '2.1.22'
swaggerCoreVersion = '1.6.14'
woodstoxVersion = '6.6.2'