Rest-java k6 tests in CI

[bilyana-gospodinova]

Description:
Add rest-java k6 tests execution as part of the workflow in order to verify the end-to-end functionality. This will be helpful to catch some issues earlier in the testing cycle. The goal is not a complete coverage of all rest-java k6 tests, so the failing ones are excluded for now.

Fixes #12161

[lfdt-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
❌ -31.86% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (290d15f)	37155	33839	91.08%
Head commit (8b149d5)	61891 (+24736)	36649 (+2810)	59.22% (-31.86%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#12243)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[steven-sheehy]

Why do we log both via logger and system.out? Should be one or the other.

[bilyana-gospodinova]

The logger is now removed.

[steven-sheehy]

Is there not an acceptance test that adds these?

[bilyana-gospodinova]

There are, but also there are steps that delete the allowances at the end or claim the airdrops, so after the execution of the acceptance tests they are no longer available. I will see what I can do without adding a bunch of new tests just to do the k6 setup.