Upstream kantra CI next steps

[aufi]

Next steps building kantra CI to consider, this should cover areas with possible tasks for upstream kantra CI tests. Expecting create issues addressing points below when we agree it should be implemented.

CI execution and stability

• Focus on long-term observability and tests stability - in progress (Marek)
  • Understand and address "random" failure E FileNotFoundError: [Errno 2] No such file or directory: '/home/runner/work/kantra-cli-tests/kantra-cli-tests/report/tackle-testapp-public-cloud-readiness/dependencies.yaml'
  • Rare maven failure due to not working github maven repo, network or auth, so deps issues are missing
• Add slack bot hooks (for certain envs - linux+windows containerless, linux containers)
• Gate kantra main repo PRs (needed add kantra build step and kantra main repo workflows)

Application analysis options

• Add binary application analysis - in progress Add jee binary app to CI #57 (OS-specific incorrect tags, Marek)
• Add non cloud-readiness target analysis - in progress Add jee binary app to CI #57
• Consider custom rules test (already exist in kantra-cli-tests repo, but not TIER0)

Test framework enhancements

• Update tests (command.py) to store kantra command output somewhere
• Do some de-duplication with existing test (and utils) in the kantra-cli-tests repo

Non-analysis use cases

• Add asset-generation tests Add asset generation tests #61