fix(acceptance-test): New acceptance test when reactive-web or api-rest component exists

[santicalleg]

Description

• Add new acceptance test when reactive-web or api-rest component exists
• Homologate api rest paths (/usecase/path) between reactive-web (with or without router) and api-rest components

Category

• Feature
• Fix
• Ci / Docs

Checklist

• The pull request is complete according to the guide of contributing
• Automated tests are written
• The documentation is up-to-date
• The pull request has a descriptive title that describes what has changed, and provides enough context for the changelog
• If the pull request has a new driven-adapter or entry-point, you should add it to docs and sh_generate_project.sh files for generated code tests.
• If the pull request has changed structural files, you have implemented an UpgradeAction according to the guide
• If the pull request has a new Gradle Task, you should add Analytics according to the guide

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
92.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[juancgalvis]

Thanks!

[app-toolkit-opensource-innersource]

🎉 This PR is included in version 3.20.11 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀