chore(deps): bump Tomcat to 10.1.29

[tasso94]

related to #4622

[psavidis]

❓ Should we add ci:webapp-integration?

screenshot

[github-actions]

Java dependency diff

🔄 camunda-root: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
 └─ 🔄 camunda-parent: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
     └─ 🔄 camunda-database-settings: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
         └─ 🔄 camunda-tomcat: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
             ├─ 🔄 camunda-tomcat-assembly: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
             │   └─ ⬆ tomcat: 10.1.25 ❓ => 10.1.30 ❓  
             └─ 🔄 camunda-bpm-tomcat: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
                 └─ 🔄 camunda-tomcat-assembly: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
                     └─ ⬆ tomcat: 10.1.25 ❓ => 10.1.30 ❓  

Module details

tomcat:10.1.25

Declared licenses: None

Links: None

tomcat:10.1.30

Declared licenses: None

Links: None

Checklist

Unique changes

• tomcat: 10.1.25 ❓ => 10.1.30 ❓

Unique additions

Developer comments

Glossary

Limitations

• The reported transitive dependencies may not always be accurate in a multi-module project.
  The SBOM file format represents a unique dependency (coordinates + type) only once. In a multi-module
  project a dependency can be declared in multiple locations with different exclusions of transitive dependencies
  or different version overrides for transitive dependencies.

Emojies

• ✔: All licenses are on the Go list
• ⚠: (At least one) license is on the Caution list
• ❌: (At least one) license is on the Stop list
• ❓: (At least one) license cannot be determined or is unknown
• ‼: Dependency has multiple licenses declared
• ⬆: New dependency version is higher than previous
• ⬇: New dependency version is lower than previous
• 🔄: Dependency version is equal and the dependencies of this component changed (e.g. when comparing snapshots)
• 🤷: The change of the dependency version can not be determined further (e.g. because the version does not follow semantic versioning)