License activation failure cause exit code 0

**Bug description**
If unity in the container got the wrong license activation file (or credentials, I guess, didn't check) it fails to build / test with exit code 0. Which is threatened as a successful run.

**How to reproduce**
- Put to secrets wrong license (outdated, another version, etc)
- Run pipeline

**Expected behavior**
- Docker should exit with non-zero code

Start by reproducing the pipeline with an invalid, outdated, or mismatched Unity license, then inspect how the container handles Unity activation and build or test failures. Done means the Docker container exits with a non-zero code when license activation fails, while successful runs retain their existing behavior.

Written by the indexing model from the issue text.