[full-ci] Chase the pipline ghost

[kobergj]

Running pipelines to find the issue for #7279

First try: Let services exit hard when they fail. This should clean up logs so the underlying issue is more visible

Second try: Use ociswrapper to restart ocis when it exits

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
77.1% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[butonic]

This changes the behavior of ocis to fail early. We should document this as now ocis might die when a race condition causes startup to fail. This is not a problem when using a service orchestrator as they will deal with restarting ocis.

We need to deal with services starting out of order and still reconnecting to each other. But that is another topic. For now, I'm happy to make CI more stable by using the wrapper (that automatically restarts ocis)

[kobergj]

Yes I 100% agree. I'll merge as is for now