feat(clearinghouse): add auto retrigger for END_CLEARINGHOUSE

[Phil91]

Description

enable maintenance worker to retrigger the clearinghouse process

Why

To enable an auto retrigger for the clearinghouse process if the END_CLEARINGHOUSE is on TODO for a certain time.

Issue

Refs: #810

Corresponding CD PR

eclipse-tractusx/portal#418

Checklist

• I have followed the contributing guidelines
• I have performed IP checks for added or updated 3rd party libraries
• I have created and linked IP issues or requested their creation by a committer
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[evegufy]

Please take care of codeql findings

[ntruchsess]

I've refactored some hard to read code, removed some reduncancy and moved code to where it belongs (calls on dbcontext into repo).
remark: not all scanner findings give good guidance to create better understandable code - e.g. implicitly selecting (caused by use of async lambda) into a task in the foreach-loop where that task is awaited at a different location might not be understud by every developer at the first glance. I did add a new factory-method that turns IEnumerable<Task> into IAsyncEnumerable which allows to await the tasks directly in the foreach.
There is one comment you should check (new unreferenced setting) and 4 scanner-findings I leave up to you to resolve ;-)

[ntruchsess]

@Phil91 : had to replace END_CLEARINGHOUSE by AWAIT_CLEARING_HOUSE_RESPONSE as per rebase on main. From my understanding that should just have been a rename without semantic changes?

[Phil91]

@Phil91 : had to replace END_CLEARINGHOUSE by AWAIT_CLEARING_HOUSE_RESPONSE as per rebase on main. From my understanding that should just have been a rename without semantic changes?

@ntruchsess correct :)

[Phil91]

I've refactored some hard to read code, removed some reduncancy and moved code to where it belongs (calls on dbcontext into repo). remark: not all scanner findings give good guidance to create better understandable code - e.g. implicitly selecting (caused by use of async lambda) into a task in the foreach-loop where that task is awaited at a different location might not be understud by every developer at the first glance. I did add a new factory-method that turns IEnumerable into IAsyncEnumerable which allows to await the tasks directly in the foreach. There is one comment you should check (new unreferenced setting) and 4 scanner-findings I leave up to you to resolve ;-)

@ntruchsess fixed the sonar findings and removed the unnecessary setting

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

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

See analysis details on SonarCloud

code-ql findings were solved