chore(deps): update dependency org.codehaus.groovy:groovy-xml to v3.0.22

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.codehaus.groovy:groovy-xml (source)	3.0.21 -> 3.0.22

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

---

PR-Codex overview

The focus of this PR is to update the groovy-xml version from 3.0.21 to 3.0.22 in the pom.xml, eo-runtime/pom.xml, and eo-maven-plugin/pom.xml files.

Detailed summary

• Updated groovy-xml version from 3.0.21 to 3.0.22 in multiple pom.xml files.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[github-actions]

The provided diff shows that the version of the "groovy-xml" dependency is being updated from "3.0.21" to "3.0.22". There are no confusions or irregularities in this part of the code, assuming that the new version "3.0.22" exists and is compatible with the rest of your project.

However, please remember that proper testing should be done after any changes, even seemingly minor ones like this, as they can sometimes result in unexpected behavior due to differences between versions.

[github-actions]

This diff shows a change in the version of the groovy-xml dependency from 3.0.21 to 3.0.22 in a Maven POM (Project Object Model) file.

There are no syntax errors or irregularities in this diff. However, whether this change is acceptable or not depends on other factors which can't be decided just by looking at this code fragment:

1. The new version (3.0.22) should exist and should be accessible in the repositories configured for the project.
2. This 3.0.22 version should be backwards compatible with 3.0.21 or the parts of the project that use groovy-xml must have been updated appropriately to handle any breaking changes in the new version.
3. There should be no known critical bugs or security vulnerabilities associated with version 3.0.22.

If you verify these points and all of them apply, the changes in this code diff could be accepted.

[github-actions]

The code snippet you provided is a type of diff (difference) that indicates a single line change in a Maven pom.xml file. This change specifically involves updating the version of the groovy-xml library from 3.0.21 to 3.0.22.

As far as the diff structure is concerned, there's no confusion or irregularity. But whether this update will work or not depends on the availability and compatibility of the new version (3.0.22) with your overall project. You would need to confirm that the new version exists, is available for downloading from your specified Maven repository, and does not introduce any breaking changes or conflicts with other dependencies in your Maven project.

[yegor256]

@rultor please, try to merge, since 23 checks have passed

[rultor]

@rultor please, try to merge, since 23 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor please, try to merge, since 23 checks have passed

@yegor256 Done! FYI, the full log is here (took me 26min)