#1748: improve IDEasy status documentation

[MarvMa]

This PR fixes #1748

Implemented changes:

• created a python script to generate a quality-status.adoc file
• the generated quality-status.adoc is beeing referenced in the readme.md and contains an overview with all the open issues for each os with a classification for blocker, bugs or features.

---

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
  with internal

[coveralls]

Coverage Report for CI Build 25716448412

Coverage increased (+0.05%) to 70.673%

Details

• Coverage increased (+0.05%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	15471
Covered Lines:	11393
Line Coverage:	73.64%
Relevant Branches:	6918
Covered Branches:	4430
Branch Coverage:	64.04%
Branches in Coverage %:	Yes
Coverage Strength:	3.11 hits per line

---

💛 - Coveralls

[jakozian]

Very nice looking quality-status documentation!

[laim2003]

Looks very good! I’ve taken a look at it now and everything looked great.
Are there already ideas on when this should be executed?
I’m thinking of an action that runs either as part of the nightly build or on every PR build, so that the file is always up to date.

[MarvMa]

Looks very good! I’ve taken a look at it now and everything looked great. Are there already ideas on when this should be executed? I’m thinking of an action that runs either as part of the nightly build or on every PR build, so that the file is always up to date.

I suppose it makes sense to run this every release to balance resource overhead and actuality